Is the TCP-code threaded?

Is the TCP-code threaded?

[Kristian Evensen]

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

Re: Is the TCP-code threaded?

[kalash nainwal]

On 2/24/07, Kristian Evensen <kristrev@ifi.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?

Re: Is the TCP-code threaded?

[Cyprien LAPLACE]

kalash nainwal wrote:
> On 2/24/07, Kristian Evensen <kristrev@ifi.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?
Hum, except if sending is delayed because of lack of windows, waiting
for ack etc. In this case, sending may be delayed to soft-irq and
single-threaded with reception (data are processed in soft-irq)..

Is this correct ?

Cyprien