From: David Miller <davem@davemloft.net>
To: johny@asimco.com.cn
Cc: kuznet@ms2.inr.ac.ru, netdev@vger.kernel.org, jmorris@namei.org,
kaber@coreworks.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.27.7-9-pae #7 SMP 1/1] networking tcp: Writing tcp socket be atomic
Date: Wed, 03 Feb 2010 08:52:49 -0800 (PST) [thread overview]
Message-ID: <20100203.085249.98326242.davem@davemloft.net> (raw)
In-Reply-To: <474C17045AA24E3F8519EE76BAB47439@JOHNYE1>
Locking belongs inside of the application, not in the kernel.
As evidenced by the fact that you had to add new socket options, the
application needs to be modified anyways.
It's therefore just as easy to add the appropriate locking to the
sequences where the application writes over the TCP socket. And
it avoids having to modify the kernel at all.
next prev parent reply other threads:[~2010-02-03 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 9:12 [PATCH 2.6.27.7-9-pae #7 SMP 1/1] networking tcp: Writing tcp socket be atomic john ye
2010-02-03 16:52 ` David Miller [this message]
2010-02-04 2:03 ` John Ye
2010-02-04 2:19 ` David Miller
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=20100203.085249.98326242.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=johny@asimco.com.cn \
--cc=kaber@coreworks.de \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).