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

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

Date:	Sat, 24 Feb 2007 14:59:52 +0530
From:	"kalash nainwal" <nirvana.code@...il.com>
To:	"Kristian Evensen" <kristrev@....uio.no>
Cc:	netdev@...r.kernel.org, linux-net@...r.kernel.org
Subject: Re: Is the TCP-code threaded?

On 2/24/07, Kristian Evensen <kristrev@....uio.no> wrote:
> 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?
>
send happes in process context, recv in interrupt context...isn't it?
-
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