tcp_write

public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed

* tcp_write_space
@ 2001-07-23  9:37 Aviv Greenberg
  2001-07-23 22:53 ` tcp_write_space Alexey Kuznetsov
  0 siblings, 1 reply; 2+ messages in thread
From: Aviv Greenberg @ 2001-07-23  9:37 UTC (permalink / raw)
  To: linux-kernel

Hi,

Why isn't the sk->callback_lock aquired in the tcp_write_space
callback ??

Is this intentional ?

-- 
	- Aviv Greeberg

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: tcp_write_space
  2001-07-23  9:37 tcp_write_space Aviv Greenberg
@ 2001-07-23 22:53 ` Alexey Kuznetsov
  0 siblings, 0 replies; 2+ messages in thread
From: Alexey Kuznetsov @ 2001-07-23 22:53 UTC (permalink / raw)
  To: deca; +Cc: linux-kernel

Hello!

> Why isn't the sk->callback_lock aquired in the tcp_write_space
> callback ??
> 
> Is this intentional ?

Yes, this lock is not required in this case because tcp_write_space()
is called only from under socket lock, which is stronger than callback_lock.
This is true _only_ for TCP sockets.

Alexey

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2001-07-24 17:05 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-07-23  9:37 tcp_write_space Aviv Greenberg
2001-07-23 22:53 ` tcp_write_space Alexey Kuznetsov

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox