netdev - Re: [PATCH] NET: Multiqueue network device support.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <46688706.9040702@intel.com>
Date:	Thu, 07 Jun 2007 15:30:30 -0700
From:	"Kok, Auke" <auke-jan.h.kok@...el.com>
To:	hadi@...erus.ca
CC:	Jeff Garzik <jeff@...zik.org>, David Miller <davem@...emloft.net>,
	kaber@...sh.net, peter.p.waskiewicz.jr@...el.com,
	netdev@...r.kernel.org,
	Jesse Brandeburg <jesse.brandeburg@...el.com>
Subject: Re: [PATCH] NET: Multiqueue network device support.

jamal wrote:
> On Thu, 2007-07-06 at 15:06 -0700, Kok, Auke wrote:
> 
>> the contention isn't between multiple tx attempts, but between e1000_clean and 
>> tx. 
> 
> I got you the first time but i think i am missing something:  given that
> the lock is used only on tx - how is that protecting the contention
> between tx and rx?

our rx interrupt/clean can trigger tx cleans, reaching the same code...

Auke
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html