From: Ben Hutchings <bhutchings@solarflare.com>
To: James Huang <jamesclhuang@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: LRO restructuring?
Date: Wed, 18 Feb 2009 19:42:43 +0000 [thread overview]
Message-ID: <1234986163.3183.14.camel@achroite> (raw)
In-Reply-To: <loom.20090218T192451-89@post.gmane.org>
On Wed, 2009-02-18 at 19:25 +0000, James Huang wrote:
> Hi Herbert,
>
> Any idea when this LRO restructuring work will be done?
> Making LRO available even when ip forwarding is enabled will significantly
> improve performace of network appliances in the data path.
Herbert has added "GRO" rather than immediately replacing the inet_lro
code. An early version of this is in 2.6.29 and there is more in
net-next-2.6 destined for 2.6.30.
> I have some questions on this:
[...]
> (3) I think bridged packets should not be LROed. Whether a packet is bridged
> or not can be based on the L2 MAC destination address. Is this how it is done?
GRO preserves enough information to reconstruct the original frames on
output, so there is no specific check for bridging. Presumably it would
be cheaper not to do use GRO if the frames are not going to hit the
TCP/IP stack though.
> (4) Does LRO work only for IPv4? Any plan to extend it to support IPv6?
IPv6 is covered.
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:[~2009-02-18 19:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 13:30 LRO restructuring? Andrew Gallatin
2008-08-11 21:03 ` David Miller
2008-08-12 11:50 ` Andrew Gallatin
2008-08-13 2:14 ` Herbert Xu
2008-08-12 0:50 ` Herbert Xu
2008-08-12 0:54 ` David Miller
2008-08-12 1:00 ` Herbert Xu
2008-08-12 1:30 ` Rick Jones
2008-08-12 1:39 ` David Miller
2008-08-12 1:53 ` Herbert Xu
2009-02-18 19:25 ` James Huang
2009-02-18 19:42 ` Ben Hutchings [this message]
2009-02-18 19:46 ` Stephen Hemminger
2009-02-19 13:53 ` Herbert Xu
2009-02-19 22:20 ` James Huang
[not found] ` <f0ed9b110902191417k2917d856q9098b304eeb7435b@mail.gmail.com>
2009-02-20 0:37 ` Herbert Xu
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=1234986163.3183.14.camel@achroite \
--to=bhutchings@solarflare.com \
--cc=jamesclhuang@gmail.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).