From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Fredrik Noring <noring@nocrew.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Improving read/write/close system call reliability when used with pthreads
Date: Sun, 12 Aug 2007 19:55:25 +0100 [thread overview]
Message-ID: <20070812195525.20dbb6fc@the-village.bc.nu> (raw)
In-Reply-To: <A94120FD-315A-45B7-A8F4-8DC8DC21279E@nocrew.org>
> POSIX appears to leave it "implementation-defined" provided I
> interpret this correctly, of course. So wouldn't it be great to make
> one of the current results a reliable feature?
Given that 99.99% of programs don't appear to care and you materially
slow down a critical path for every read and write I'm skeptical.
Teaching the pipe code specifically to behave more nicely in this case
might be worthwhile (and as it happens with sockets in the same case you
can use shutdown() before close to get your preferred behaviour)
Alan
next prev parent reply other threads:[~2007-08-12 18:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 13:03 Fredrik Noring
2007-08-12 14:17 ` Paul Jackson
2007-08-12 18:30 ` [PATCH] " Fredrik Noring
2007-08-12 15:13 ` Alan Cox
2007-08-12 16:33 ` Fredrik Noring
2007-08-12 18:55 ` Alan Cox [this message]
2007-08-12 19:19 ` Fredrik Noring
2007-08-13 3:14 ` David Schwartz
2007-08-13 6:50 ` Fredrik Noring
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=20070812195525.20dbb6fc@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=noring@nocrew.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®