* Is the TCP-code threaded?
@ 2007-02-23 23:38 Kristian Evensen
2007-02-24 9:29 ` kalash nainwal
0 siblings, 1 reply; 3+ messages in thread
From: Kristian Evensen @ 2007-02-23 23:38 UTC (permalink / raw)
To: netdev; +Cc: linux-net
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Is the TCP-code threaded?
2007-02-23 23:38 Is the TCP-code threaded? Kristian Evensen
@ 2007-02-24 9:29 ` kalash nainwal
2007-02-24 11:40 ` Cyprien LAPLACE
0 siblings, 1 reply; 3+ messages in thread
From: kalash nainwal @ 2007-02-24 9:29 UTC (permalink / raw)
To: Kristian Evensen; +Cc: netdev, linux-net
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?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Is the TCP-code threaded?
2007-02-24 9:29 ` kalash nainwal
@ 2007-02-24 11:40 ` Cyprien LAPLACE
0 siblings, 0 replies; 3+ messages in thread
From: Cyprien LAPLACE @ 2007-02-24 11:40 UTC (permalink / raw)
To: kalash nainwal; +Cc: netdev, linux-net
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-02-24 11:40 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-02-23 23:38 Is the TCP-code threaded? Kristian Evensen
2007-02-24 9:29 ` kalash nainwal
2007-02-24 11:40 ` Cyprien LAPLACE
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).