netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Lemoine <eric.lemoine@gmail.com>
To: Andi Kleen <ak@suse.de>
Cc: davem@redhat.com, netdev@oss.sgi.com
Subject: Re: [PATCH] LLTX for tg3
Date: Sun, 12 Sep 2004 19:06:26 +0200	[thread overview]
Message-ID: <5cac192f040912100616feb28a@mail.gmail.com> (raw)
In-Reply-To: <20040907121841.GA4398@wotan.suse.de>

> Add LLTX suppor to tg3.  Locking was already safe for it, so only
> trivial changes.

tg3_set_rx_mode() (dev->set_multicast_list()) and tg3_start_xmit()
used to synchronise thanks to dev->lock_xmit. With your LLTX patches
they don't synchronise anymore (I don't think tg3_set_rx_mode() grabs
tp->tx_lock) ; isn't it an issue?

PS: your LLTX patch to e1000 seems to have the needed extra locking in
e1000_set_multi() though.

> Depends on the LLTX patch sent earlier.
> 
> diff -u linux-2.6.8/drivers/net/tg3.c-o linux-2.6.8/drivers/net/tg3.c
> --- linux-2.6.8/drivers/net/tg3.c-o     2004-09-04 13:10:46.000000000 +0000
> +++ linux-2.6.8/drivers/net/tg3.c       2004-09-07 08:17:36.000000000 +0000
> @@ -3036,7 +3036,11 @@
>          * So we really do need to disable interrupts when taking
>          * tx_lock here.
>          */
> -       spin_lock_irqsave(&tp->tx_lock, flags);
> +       local_irq_save(flags);
> +       if (!spin_trylock(&tp->tx_lock)) {
> +               local_irq_restore(flags);
> +               return -1;
> +       }
> 
>         /* This is a hard error, log it. */
>         if (unlikely(TX_BUFFS_AVAIL(tp) <= (skb_shinfo(skb)->nr_frags + 1))) {
> @@ -8255,6 +8259,7 @@
> 
>         if (pci_using_dac)
>                 dev->features |= NETIF_F_HIGHDMA;
> +       dev->features |= NETIF_F_LLTX;
>  #if TG3_VLAN_TAG_USED
>         dev->features |= NETIF_F_HW_VLAN_TX | NETIF_F_HW_VLAN_RX;
>         dev->vlan_rx_register = tg3_vlan_rx_register;
> 
> 

-- 
Eric

  reply	other threads:[~2004-09-12 17:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-07 12:18 [PATCH] LLTX for tg3 Andi Kleen
2004-09-12 17:06 ` Eric Lemoine [this message]
2004-09-12 23:45   ` David S. 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=5cac192f040912100616feb28a@mail.gmail.com \
    --to=eric.lemoine@gmail.com \
    --cc=ak@suse.de \
    --cc=davem@redhat.com \
    --cc=netdev@oss.sgi.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).