From: Ben Hutchings <bhutchings@solarflare.com>
To: Marc Aurele La France <tsi@ualberta.ca>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
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 18:57:27 +0100 [thread overview]
Message-ID: <1282672647.2302.15.camel@achroite.uk.solarflarecom.com> (raw)
In-Reply-To: <alpine.WNT.2.00.1008240856170.2000@cluij.ucs.ualberta.ca>
On Tue, 2010-08-24 at 09:14 -0600, Marc Aurele La France wrote:
> 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.
[...]
Stephen and I are not talking about IP fragmentation, but about the
ability to append 'fragments' to an skb rather than putting the entire
packet payload in a linear buffer. See
<http://vger.kernel.org/~davem/skb_data.html>.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2010-08-24 17:57 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
2010-08-24 17:57 ` Ben Hutchings [this message]
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=1282672647.2302.15.camel@achroite.uk.solarflarecom.com \
--to=bhutchings@solarflare.com \
--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=tsi@ualberta.ca \
--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