netdev - localhost network processing on smp machines

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-next>] [day] [month] [year] [list]

Date:	Mon, 5 Nov 2007 20:48:39 +0000
From:	"Matthew Faulkner" <matthew.faulkner@...il.com>
To:	netdev@...r.kernel.org
Subject: localhost network processing on smp machines

I'm probably being stupid and very confused here. Appologies if it is
a stupid question.

For a particular test I assign a client to core 1 and a server to core
0. My first assumption was all the sending side kernel TCP/IP
processing will be done on core 1 and all the receiving side
processing on core 0. However, having looked at the linux TCP/IP code,
more specifically the loopback device code, when the loopbacks
dev_queue_xmit function gets called it simply passes the skb to the
netif_rx function. Therefore my question is thus, when i assign the
sending / receiving side to different cores is the actual TCP/IP
processing done the assigned sending / receiving cores ? or is TCP/IP
processing done on the sending side only until a certain point? or is
it simply a single core that does all the TCP/IP processing. If it's
the first two and you have any idea, could you point me where in the
kernel the cores the processing swap over.

Thanks for your help
-
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