Re: [PATCH] tcpdump may trace some outbound packets twice.

David S. Miller <[email protected]> wrote:
> 
> Other implementation possibility suggestions welcome :-)

I see two possibilities:

1) Move the af_packet hook into the NIC driver.
2) Rethink the lockless tx setup.  If all NICs followed the tg3 and
   replaced spin_lock_irqsave with spin_lock then we should be able
   to go back to just using the xmit_lock.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] tcpdump may trace some outbound packets twice.
    • From: Patrick McHardy <[email protected]>

• References:
  • Re: [PATCH] tcpdump may trace some outbound packets twice.
    • From: "David S. Miller" <[email protected]>

• Prev by Date: Re: [PATCH 5/6] Have ia64 use add_active_range() and free_area_init_nodes
• Next by Date: Re: unknown io writes in 2.6.16
• Previous by thread: Re: [PATCH] tcpdump may trace some outbound packets twice.
• Next by thread: Re: [PATCH] tcpdump may trace some outbound packets twice.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]