netdev - Re: will 2 cpu simultaneously process packets which have same hash value on multiqueue nic?

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <1274356826.4046.29.camel@edumazet-laptop>
Date:	Thu, 20 May 2010 14:00:26 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	eilong@...adcom.com
Cc:	Jon Zhou <Jon.Zhou@...u.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: will 2 cpu simultaneously process packets which have same hash
 value on multiqueue nic?

Le jeudi 20 mai 2010 à 14:46 +0300, Eilon Greenstein a écrit :
> On Wed, 2010-05-19 at 22:37 -0700, Jon Zhou wrote:
> > will 2 cpu simultaneously  process packets which have same hash value on multiqueue nic?
> > 
> > let 's take broadcom 57711 bnx2x_main.c as an example:
> > 
> > #1 packet1->queue=1
> > #2 packet2->queue=1
> > 
> > will cpu1 and cpu2 execute the function " bnx2x_rx_int" in parallel, to receive packet1 & packet2
> Both packets will be handled by the same queue and the queue processing
> is serialized - so the packets will be handled one after the other.

I am scratching my head to understand both the question and your
answer...

if cpu1 is handling an interrupt, cpu2 cannot handle an interrupt at the
same time for same queue. It must be for a different queue.

Therefore, packets will be handled in parallel.

Serialization might be done later, at socket layer to queue packets in a
receive queue for example, if both packets must be delivered on same
socket.



--
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