From: David Miller <davem@davemloft.net>
To: therbert@google.com
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH] NIU support for skb->rxhash
Date: Fri, 23 Apr 2010 13:28:01 -0700 (PDT) [thread overview]
Message-ID: <20100423.132801.192648533.davem@davemloft.net> (raw)
In-Reply-To: <h2z65634d661004230832o4f7a6d35ub207bc301ee8925c@mail.gmail.com>
From: Tom Herbert <therbert@google.com>
Date: Fri, 23 Apr 2010 08:32:02 -0700
>> I looked into implementing this and it doesn't work. The
>> problem is GRO want's to look into the packet very early
>> and we want to batch GRO a set of packets into a big packet
>> before shooting them over to a remote cpu.
>>
>
> Can you reconsider? :-) The majority of our servers see packet loads
> which don't allow for much batching (a lot of small RPC messages), so
> for those GRO is mostly unnecessary overhead and mechanisms that
> improve unbatched packet performance are compelling. Also, if a
> device already does LRO, I don't see that GRO could add a lot of value
> anyway.
LRO is extremely discouraged, because it has to be disabled
when any form of forwarding or bridging is enabled. LRO is
done such that the input packet stream cannot be reconstituted
on transmit.
GRO on the other hand, allows proper reconstitution of the input
packet stream so it can be enabled unconditionally.
We are encouraging hardware manufacturers to tweak their receive
batching offload such that it matches the rules imposed by GRO
which allow proper reconsitution on transmit.
The fact is the code patch is there and it is going to be enabled all
the time, so we have to cope with it.
next prev parent reply other threads:[~2010-04-23 20:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 11:21 [PATCH] NIU support for skb->rxhash David Miller
2010-04-22 11:43 ` Eric Dumazet
2010-04-22 21:19 ` David Miller
2010-04-23 8:14 ` David Miller
2010-04-23 15:32 ` Tom Herbert
2010-04-23 20:28 ` David Miller [this message]
2010-04-22 16:21 ` Stephen Hemminger
2010-04-22 21:36 ` David Miller
2010-04-22 22:11 ` Stephen Hemminger
2010-04-22 22:24 ` David Miller
2010-04-22 21:37 ` David Miller
2010-04-22 22:53 ` David Miller
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=20100423.132801.192648533.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.com \
/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;
as well as URLs for NNTP newsgroup(s).