From: Jeff Garzik <jeff@garzik.org>
To: Brice Goglin <brice@myri.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/1] myri10ge: correctly detect when TSO should be used
Date: Wed, 28 Mar 2007 02:19:44 -0400 [thread overview]
Message-ID: <460A0900.1030609@garzik.org> (raw)
In-Reply-To: <4609768D.8020309@myri.com>
Brice Goglin wrote:
> Correctly detect when TSO should be used on transmit by looking at the
> skb->gso_size rather than seeing if the frame was larger than our MTU.
> The old method causes problems when a host with a large (jumbo) MTU is
> sending to a host with a small (standard) MTU.
>
> Signed-off-by: Brice Goglin <brice@myri.com>
> ---
> drivers/net/myri10ge/myri10ge.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
applied to #upstream-fixes
prev parent reply other threads:[~2007-03-28 6:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 19:52 [PATCH 0/1] myri10ge fix for 2.6.21 Brice Goglin
2007-03-27 19:54 ` [PATCH 1/1] myri10ge: correctly detect when TSO should be used Brice Goglin
2007-03-27 19:54 ` Brice Goglin
2007-03-28 6:19 ` Jeff Garzik [this message]
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=460A0900.1030609@garzik.org \
--to=jeff@garzik.org \
--cc=brice@myri.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).