From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] devip connect error state
Date: Thu, 9 Aug 2007 09:38:37 +0100 [thread overview]
Message-ID: <a467fec1835875002df56b3d5df90693@terzarima.net> (raw)
In-Reply-To: <775b8d190708082347t51a127cxcd90c884d4547223@mail.gmail.com>
>"why?" when it comes to sockets has always been
>swept under the carpet for all known functionality.
one surprise for me is that linux locks the socket
during i/o (good), but releases it in certain cases, so
writes from several processes are interleaved every so often (bad),
so it might just as well not bother with the overall lock anyway.
next prev parent reply other threads:[~2007-08-09 8:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 20:59 Eric Van Hensbergen
2007-08-08 21:14 ` ron minnich
2007-08-08 21:19 ` Charles Forsyth
2007-08-09 3:33 ` Eric Van Hensbergen
2007-08-09 6:47 ` Bruce Ellis
2007-08-09 8:38 ` Charles Forsyth [this message]
2007-08-08 21:48 ` Charles Forsyth
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=a467fec1835875002df56b3d5df90693@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@cse.psu.edu \
/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).