From: Marc Aurele La France <tsi@ualberta.ca>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
"Pekka Savola (ipv6)" <pekkas@netcore.fi>,
James Morris <jmorris@namei.org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Patrick McHardy <kaber@trash.net>
Subject: Re: RFC: MTU for serving NFS on Infiniband
Date: Tue, 24 Aug 2010 09:14:54 -0600 (Mountain Daylight Time) [thread overview]
Message-ID: <alpine.WNT.2.00.1008240856170.2000@cluij.ucs.ualberta.ca> (raw)
In-Reply-To: <20100823080543.319143e3@nehalam>
On Mon, 23 Aug 2010, Stephen Hemminger wrote:
> On Mon, 23 Aug 2010 08:44:37 -0600 (MDT)
> Marc Aurele La France <tsi@ualberta.ca> 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.
+----------------------------------+----------------------------------+
| Marc Aurele La France | work: 1-780-492-9310 |
| Academic Information and | fax: 1-780-492-1729 |
| Communications Technologies | email: tsi@ualberta.ca |
| 352 General Services Building +----------------------------------+
| University of Alberta | |
| Edmonton, Alberta | Standard disclaimers apply |
| T6G 2H1 | |
| CANADA | |
+----------------------------------+----------------------------------+
next prev parent reply other threads:[~2010-08-24 15:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 14:44 RFC: MTU for serving NFS on Infiniband Marc Aurele La France
2010-08-23 15:05 ` Stephen Hemminger
2010-08-24 15:14 ` Marc Aurele La France [this message]
2010-08-24 17:57 ` Ben Hutchings
2010-08-24 19:49 ` Marc Aurele La France
2010-08-24 20:09 ` Eric Dumazet
2010-08-24 20:33 ` Marc Aurele La France
2010-08-24 22:20 ` Ben Hutchings
2010-08-24 22:39 ` Stephen Hemminger
2010-08-25 5:54 ` Eric Dumazet
2010-08-25 12:10 ` Alexey Kuznetsov
2010-08-25 12:17 ` Eric Dumazet
2010-08-26 11:40 ` Marc Aurele La France
2010-08-26 11:57 ` Eric Dumazet
2010-08-26 14:43 ` Marc Aurele La France
2010-08-26 23:53 ` Stephen Hemminger
2010-08-27 0:06 ` David Miller
2010-08-27 16:20 ` Roland Dreier
2010-08-27 17:16 ` Roland Dreier
2010-08-27 17:53 ` Marc Aurele La France
2010-08-26 14:58 ` Chuck Lever
2010-09-30 18:50 ` Marc Aurele La France
2010-08-23 15:12 ` Ben Hutchings
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.WNT.2.00.1008240856170.2000@cluij.ucs.ualberta.ca \
--to=tsi@ualberta.ca \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
--cc=shemminger@vyatta.com \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox