From: David Miller <davem@davemloft•net>
To: mchan@broadcom•com
Cc: herbert@gondor•apana.org.au, jk@blackdown•de, netdev@vger•kernel.org
Subject: Re: [PATCH 4/5] tg3: Add TSO workaround using GSO
Date: Thu, 29 Jun 2006 20:16:08 -0700 (PDT) [thread overview]
Message-ID: <20060629.201608.90120890.davem@davemloft.net> (raw)
In-Reply-To: <1151630967.21798.20.camel@rh4>
From: "Michael Chan" <mchan@broadcom•com>
Date: Thu, 29 Jun 2006 18:29:27 -0700
> Use GSO to workaround a rare TSO bug on some chips. This hardware
> bug may be triggered when the TSO header size is greater than 80
> bytes. When this condition is detected in a TSO packet, the driver
> will use GSO to segment the packet to workaround the hardware bug.
>
> Thanks to Juergen Kreileder <jk@blackdown•de> for reporting the
> problem and collecting traces to help debug the problem.
>
> And thanks to Herbert Xu <herbert@gondor•apana.org.au> for providing
> the GSO mechanism that happens to be the perfect workaround for this
> problem.
>
> Signed-off-by: Michael Chan <mchan@broadcom•com>
Looks really nice. Applied, thanks a lot.
prev parent reply other threads:[~2006-06-30 3:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 1:29 [PATCH 4/5] tg3: Add TSO workaround using GSO Michael Chan
2006-06-30 3:16 ` David Miller [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=20060629.201608.90120890.davem@davemloft.net \
--to=davem@davemloft$(echo .)net \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=jk@blackdown$(echo .)de \
--cc=mchan@broadcom$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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