From: Eric Dumazet <eric.dumazet@gmail.com>
To: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
Ben Hutchings <bhutchings@solarflare.com>,
Marc Aurele La France <tsi@ualberta.ca>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
"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: Wed, 25 Aug 2010 14:17:43 +0200 [thread overview]
Message-ID: <1282738663.2487.207.camel@edumazet-laptop> (raw)
In-Reply-To: <20100825121058.GA28498@ms2.inr.ac.ru>
Le mercredi 25 août 2010 à 16:10 +0400, Alexey Kuznetsov a écrit :
> Hello!
>
> > It is, but ip_append_data() is allocating a huge head if MTU is huge.
>
> Hmm, strange, as I remember, it was supposed to work right.
>
> If the device supports SG (which is required to accept non-linear skbs anyway),
> then ip_append_* should allocate skbs not rounded up to mtu and we should
> allocate small skb with NFS header only. Does not it work?
>
> I can only guess one possible trap: people could do _one_ huge ip_append_data()
> (instead of "planned" scenario, when the header is sent with ip_append_data()
> and the following payload is appended with ip_append_page()). Huge ip_append_data()
> will generate huge skb indeed. Is this the problem?
>
>
> BTW this issue could be revisited and this "will generate huge" can be reconsidered.
> Automatic generation of fragmented skbs was deliberately suppressed, because it was
> found that all devices existing at the moment when this code was written
> are strongly biased against SG. Current code tries to _avoid_ generating
> non-linear skbs, unless it is intended for zero-copy, which compensated
> bias against SG. Modern hardware should work better.
>
> Alexey
Hi Alexey,
Few hours ago, I privately asked to Marc Aurele if its infiniband device
was supporting NETIF_F_SG in its features ;)
Thanks !
next prev parent reply other threads:[~2010-08-25 12:17 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 [this message]
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=1282738663.2487.207.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=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