From: Jeff Garzik <jgarzik@pobox.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH,RFT] 8139cp TSO support
Date: Sun, 29 Aug 2004 19:02:17 -0400 [thread overview]
Message-ID: <41326079.9090402@pobox.com> (raw)
In-Reply-To: <20040829222831.GA9496@electric-eye.fr.zoreil.com>
Francois Romieu wrote:
> Jeff Garzik <jgarzik@pobox.com> :
> [...]
>
>>Also, the r8169 implementation should be similar, if someone (Francois?)
>>wants to tackle it.
>
>
> I'll copy and test it tomorrow on r8169 if nobody beats me.
>
> On a related note, 8139cp probably wants something like the patch below for
> the usual SG handling (on top of 2.6.9-rc1 + -mm1 + TSO patch):
>
> - suspicious length in pci_unmap_single;
> - wait for the last frag before freeing the relevant skb;
> - no need to crash when facing some unexpected csum combination.
Looks OK except for
> diff -puN drivers/net/8139cp.c~8139cp-010 drivers/net/8139cp.c
> --- linux-2.6.9-rc1/drivers/net/8139cp.c~8139cp-010 2004-08-29 23:47:07.000000000 +0200
> +++ linux-2.6.9-rc1-fr/drivers/net/8139cp.c 2004-08-30 00:16:13.000000000 +0200
> @@ -807,7 +807,6 @@ static int cp_start_xmit (struct sk_buff
>
> cp->tx_skb[entry].skb = skb;
> cp->tx_skb[entry].mapping = mapping;
> - cp->tx_skb[entry].frag = 0;
> entry = NEXT_TX(entry);
> } else {
> struct cp_desc *txd;
You definitely want to set .len on the no-frags path...
next prev parent reply other threads:[~2004-08-29 23:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-29 21:22 [PATCH,RFT] 8139cp TSO support Jeff Garzik
2004-08-29 22:28 ` Francois Romieu
2004-08-29 23:02 ` Jeff Garzik [this message]
2004-08-30 21:52 ` Francois Romieu
2004-08-30 21:56 ` [PATCH 2.6.9-rc1-mm1-tso 1/2] 8139cp: SG support fixes Francois Romieu
2004-08-30 21:58 ` [PATCH 2.6.9-rc1-mm1-tso 2/2] 8139cp: DAC support fix Francois Romieu
2004-08-31 7:19 ` Jeff Garzik
2004-08-31 7:20 ` [PATCH 2.6.9-rc1-mm1-tso 1/2] 8139cp: SG support fixes Jeff Garzik
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=41326079.9090402@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.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).