netdev - Is the TCP-code threaded?

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

Message-id: <45DF7B13.6040407@ifi.uio.no>
Date:	Sat, 24 Feb 2007 01:38:59 +0200
From:	Kristian Evensen <kristrev@....uio.no>
To:	netdev@...r.kernel.org
Cc:	linux-net@...r.kernel.org
Subject: Is the TCP-code threaded?

Hello,

I have been looking quite deeply into the TCP-code, but there is one 
thing I simply dont manage to understand. Can the code process more than 
one skb on a socket at the time, or is it strictly one and one?

E.g say that you are going to send something (an skb), and you recieve 
an ack at the same time. Will the kernel finish whatever of the two 
comes first (say, finish sending) or can it, in the middle of treating 
the new packet to send, do a switch and process the ack?

Thanks,
Kristian
-
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