mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Lehmann <pcg@goof.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Paul Marquis <pmarquis@iname.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: select() bug
Date: Fri, 3 Nov 2000 08:05:24 +0100	[thread overview]
Message-ID: <20001103080524.E29820@fuji.laendle> (raw)
In-Reply-To: <3A01FC44.8A43FE8B@iname.com> <E13rUD4-00026g-00@the-village.bc.nu>
In-Reply-To: <E13rUD4-00026g-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Nov 02, 2000 at 11:55:52PM +0000

On Thu, Nov 02, 2000 at 11:55:52PM +0000, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > - If I'm correct that pipes have a 4K kernel buffer, then writing 1
> > byte shouldn't cause this situation, as the buffer is well more than
> > half empty.  Is this still a bug?
> 
> The pipe code uses totally full/empty. Im not sure why that was chosen

Just a quick guess: maybe because of the POSIX atomicity guarantees (if
select returned, write might have to block which is not what is expected),
and maybe this limitation was used not only on write but on read (Although
it's not necessary on the read side, AFAIK).

-- 
      -----==-                                             |
      ----==-- _                                           |
      ---==---(_)__  __ ____  __       Marc Lehmann      +--
      --==---/ / _ \/ // /\ \/ /       pcg@opengroup.org |e|
      -=====/_/_//_/\_,_/ /_/\_\       XX11-RIPE         --+
    The choice of a GNU generation                       |
                                                         |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-11-03  7:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-02 22:11 Paul Marquis
2000-11-02 22:27 ` Alan Cox
2000-11-02 22:42   ` Richard B. Johnson
2000-11-02 22:58     ` Paul Marquis
2000-11-03  0:53       ` Richard B. Johnson
2000-11-03  5:00         ` Paul Marquis
2000-11-03 13:05           ` Richard B. Johnson
2000-11-02 22:53   ` Paul Marquis
2000-11-02 22:58     ` Alan Cox
2000-11-02 23:08       ` Paul Marquis
2000-11-02 23:20         ` Alan Cox
2000-11-02 23:44           ` Paul Marquis
2000-11-02 23:46             ` David S. Miller
2000-11-02 23:52               ` David S. Miller
2000-11-03  0:05                 ` David S. Miller
2000-11-03  0:38                   ` H. Peter Anvin
2000-11-03  0:13                 ` H. Peter Anvin
2000-11-03  0:04               ` H. Peter Anvin
2000-11-02 23:53             ` H. Peter Anvin
2000-11-03  0:01               ` Alan Cox
2000-11-02 23:55             ` Alan Cox
2000-11-03  5:52               ` dean gaudet
2000-11-03  7:05               ` Marc Lehmann [this message]
2000-11-05 16:14 Stanislav Meduna

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=20001103080524.E29820@fuji.laendle \
    --to=pcg@goof.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmarquis@iname.com \
    /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®