linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* lock_sock and friends !
@ 2003-07-16  7:13 Nagendra Singh Tomar
  0 siblings, 0 replies; only message in thread
From: Nagendra Singh Tomar @ 2003-07-16  7:13 UTC (permalink / raw)
  To: linux-kernel


I posted this on linux-net and did not get any reply, hoping to get a  
reply here ..


---------- Forwarded message ----------
Date: Tue, 15 Jul 2003 11:52:35 +0530
From: "Tomar, Nagendra" <nagendra_tomar@adaptec.com>
To: linux-net@vger.kernel.org
Subject: lock_sock and friends !

Hi,
   From reading the Linux 2.4 networking code I can figure out that any 
activity that can change the state of the socket (it can be sequence 
numbers getting updated or geting more free sndbuf memory because of
some 
packet on the retransmission queue being ACKed) is done after taking the

socket lock (lock_sock from user context and bh_lock_sock from BH 
context).
I would like some authority on this to confirm this. Is the following 
statement true.
At any time (even on SMP machines) only one piece of the code will be 
working on a socket. Of course the piece of code in question is one that

changes the state of the socket, either by processing a newly received 
packet or by calling tcp_free_skb() to add to the free socket memory.

If any clarification is needed pls feel free to contact me.

Any comments are highly welcome.

Thanx
tomar

-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html



^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2003-07-16  6:25 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-07-16  7:13 lock_sock and friends ! Nagendra Singh Tomar

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).