From: Stephen Hemminger <shemminger@vyatta.com>
To: Marc Aurele La France <tsi@ualberta.ca>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Ben Hutchings <bhutchings@solarflare.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: Thu, 26 Aug 2010 16:53:59 -0700 [thread overview]
Message-ID: <20100826165359.3b79b27d@nehalam> (raw)
In-Reply-To: <alpine.WNT.2.00.1008260835020.2008@cluij.ucs.ualberta.ca>
On Thu, 26 Aug 2010 08:43:42 -0600 (Mountain Daylight Time)
Marc Aurele La France <tsi@ualberta.ca> wrote:
> On Thu, 26 Aug 2010, Eric Dumazet wrote:
> > Le jeudi 26 août 2010 à 05:40 -0600, Marc Aurele La France a écrit :
>
> >> Steady now. There's no need to YELL nor be arrogant. You and I both know
> >> there's a place for NFS over UDP. That's not changing any time soon. While
> >> I'm aware of the issue you brought up, it is separate from the one at hand in
> >> this discussion.
>
> >> I do want to thank you, however, for reminding me of TCP. It's something
> >> 20/20 hindsight says I should have checked out before starting this thread.
> >> Logistically, it'll be a few days before I can do so though. If that allows
> >> me to increase the MTU all the way up to 65520, then this UDP thing will
> >> likely remain unresolved.
>
> > Unfortunately, your infiniband device lacks NETIF_F_SG support.
>
> Oh, the device itself probably has something similar, but ipoib
> (IP-over-Infiniband) doesn't export that capability.
>
> > MTU a bit larger than PAGE_SIZE-overhead will need high order
> > allocations ?
>
> Right. And a 65520 MTU allocates sk_buff's with 128K contiguous payloads.
Infiniband device driver needs to be fixed to do SG and checksum offload.
Otherwise it is insane to try and run large MTU over it. I even wonder if
the dev_change_mtu() function should reject > PAGESIZE mtu for devices
that don't do scatter/gather or at least a raise a warning.
next prev parent reply other threads:[~2010-08-26 23:54 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
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 [this message]
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=20100826165359.3b79b27d@nehalam \
--to=shemminger@vyatta.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--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=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