From: Rick Jones <rick.jones2@hp.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: mark1smi@us.ibm.com, "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: send(), sendmsg(), sendto() not thread-safe
Date: Mon, 15 May 2006 17:02:35 -0700 [thread overview]
Message-ID: <4469169B.401@hp.com> (raw)
In-Reply-To: <20060515163545.4e3d755a@localhost.localdomain>
>>I presume this is only for "blocking" sockets? I cannot at least off
>>the top of my head see how a stack could offer it on non-blocking sockets.
>
>
> The test seems to be based on sending a big message. In this case,
> on non-blocking sockets, the send call will return partial status. The
> return from the system call will be less than the number of bytes requested.
Right, and at that point it is already too late to do anything about
keeping some other thread of execution from shoving _its_ bytes into the
socket before the rest of the first sends' can be put there.
(Perhaps I'm preaching to the choir)
rick jones
next prev parent reply other threads:[~2006-05-16 0:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OFE8460E54.0C8D85D8-ON8525716F.0074F22F-8825716F.0076D537@us.ibm.com>
2006-05-15 22:49 ` send(), sendmsg(), sendto() not thread-safe David S. Miller
2006-05-15 23:17 ` Rick Jones
2006-05-15 23:35 ` Stephen Hemminger
2006-05-16 0:02 ` Rick Jones [this message]
[not found] <OFA7F8723C.2DDF9383-ON85257170.00014BE5-88257170.00019BEA@us.ibm.com>
2006-05-16 0:43 ` Rick Jones
2006-05-16 1:50 ` Mark A Smith
2006-05-16 16:24 ` Mike Stroyan
2006-05-17 17:25 Benjamin Reed
2006-05-17 18:00 ` Christopher Friesen
2006-05-17 18:21 ` Benjamin Reed
2006-05-17 18:52 ` Rick Jones
2006-05-17 19:06 ` Benjamin Reed
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=4469169B.401@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=mark1smi@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.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).