[lkml]   [2010]   [Aug]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: RFC: MTU for serving NFS on Infiniband
On Mon, 23 Aug 2010, Stephen Hemminger wrote:
> On Mon, 23 Aug 2010 08:44:37 -0600 (MDT)
> Marc Aurele La France <> wrote:
>> In regrouping for my next tack at this, I noticed that all stack traces go
>> through ip_append_data(). This would be ipv6_append_data() in the IPv6 case.
>> A _very_ rough draft that would have ip_append_data() temporarily drop down
>> to a smaller fake MTU follows ...

> Why doesn't NFS generate page size fragments? Does Infiniband or your
> device not support this? Any thing that requires higher order allocation
> is going to unstable under load. Let's fix the cause not the apply bandaid
> solution to the symptom.

From what I can tell, IP fragmentation is done centrally.

The MTU is a device attribute, yes. But, here, it is ip_append_data(),
not NFS nor the device driver, whose responsibility it is to break up the
payload into fragments, either by itself or using any facility supported
by the adapter. What I'm saying is that there's no reason to require all
fragments, except the last, to be MTU-sized. The RFCs I've looked at
allow them to be shorter which can be used to advantage when MTU-sized
fragments cannot be allocated in a memory fragmentation scenario, instead
of reporting an error.


| Marc Aurele La France | work: 1-780-492-9310 |
| Academic Information and | fax: 1-780-492-1729 |
| Communications Technologies | email: |
| 352 General Services Building +----------------------------------+
| University of Alberta | |
| Edmonton, Alberta | Standard disclaimers apply |
| T6G 2H1 | |
| CANADA | |

 \ /
  Last update: 2010-08-24 17:23    [W:0.096 / U:0.924 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site