From: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
To: deca@netvision.net.il
Cc: linux-kernel@vger.kernel.org
Subject: Re: tcp_write_space
Date: Tue, 24 Jul 2001 02:53:10 +0400 (MSD) [thread overview]
Message-ID: <200107232253.CAA07056@mops.inr.ac.ru> (raw)
In-Reply-To: <01072312370200.19071@aviv_linuxddd> from "Aviv Greenberg" at Jul 23, 1 01:45:00 pm
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
prev parent reply other threads:[~2001-07-24 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 9:37 tcp_write_space Aviv Greenberg
2001-07-23 22:53 ` Alexey Kuznetsov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200107232253.CAA07056@mops.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=deca@netvision.net.il \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®