From: Jan-Bernd Themann <ossthema@de.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: Thomas Klein <tklein@de.ibm.com>, Jeff Garzik <jeff@garzik.org>,
Jan-Bernd Themann <themann@de.ibm.com>,
netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-ppc <linuxppc-dev@ozlabs.org>,
Christoph Raisch <raisch@de.ibm.com>,
Marcus Eder <meder@de.ibm.com>,
Andrew Gallatin <gallatin@myri.com>,
Stefan Roscher <stefan.roscher@de.ibm.com>
Subject: [PATCH 0/1] lro: Generic Large Receive Offload for TCP traffic
Date: Fri, 3 Aug 2007 14:41:14 +0200 [thread overview]
Message-ID: <200708031441.14780.ossthema@de.ibm.com> (raw)
Hi,
I think this patch could be the final version for now. It has been tested
on two platforms (power and x86_64) and works very well.
Apart from David Miller and Evgeniy Polaykov, we'd like to thank especially
Andrew Gallatin for his great reviews and help to make that happen.
After some discussion we decided to post the LRO patch separately from the
driver patches. Our final driver patches for LRO will be posted later with
some additional fixes for upstream inclusion to the netdev git.
However, I'll also post our LRO patch for the driver today as an example
of how to use this interface.
Thanks a lot,
Jan-Bernd
[PATCH 1/1] lro: Generic Large Receive Offload for TCP traffic
Changes to http://www.spinics.net/lists/netdev/msg37084.html
1) Fixed the LRO_MAX_PG_HLEN bug
2) skb->ip_summed can now be defined by driver for aggregated packets
3) The problem that the "ramp up" for tcp connections between machines
with different MTU size (1500 vs 9000) is very slow has been fixed
by setting skb->gso_size.
4) Checksum problem for little endian machines has been fixed
5) missing additon of vlan_hdr_len for TCP header determination has been added.
next reply other threads:[~2007-08-03 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 12:41 Jan-Bernd Themann [this message]
2007-08-09 6:11 ` [PATCH 0/1] lro: Generic Large Receive Offload for TCP traffic David Miller
2007-08-09 6:31 ` Jeff Garzik
2007-08-09 7:03 ` 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=200708031441.14780.ossthema@de.ibm.com \
--to=ossthema@de.ibm.com \
--cc=davem@davemloft.net \
--cc=gallatin@myri.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=meder@de.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=raisch@de.ibm.com \
--cc=stefan.roscher@de.ibm.com \
--cc=themann@de.ibm.com \
--cc=tklein@de.ibm.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).