9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] read9pmsg usage
Date: Tue, 11 Aug 2015 16:48:14 +0100	[thread overview]
Message-ID: <CAOw7k5h7o+pCy5TABBtXRgBATqPsRac45_WXttevGzbqLvTg+w@mail.gmail.com> (raw)
In-Reply-To: <CAHL7psFD9_xWyfPTbh0tCY80=KfRUzfkh5rm_Fij8WJzw2NmJg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 732 bytes --]

On 10 August 2015 at 15:11, Giacomo Tesio <giacomo@tesio.it> wrote:

> /*
>  * reading from a pipe or a network device
>  * will give an error after a few eof reads.
>  * however, we cannot tell the difference
>  * between a zero-length read and an interrupt
>  * on the processes writing to us,
>  * so we wait for the error.
>  */
>
>
it's doubly odd, because there's no reason for an interrupted writer to go
to the lengths of writing an empty record as a consequence of being
interrupted. it will waserror out in the writer, so why should an empty
Block end up on the underlying Queue?
In fact, an interrupted writer in devmnt will start the flush(5) protocol,
so it will be writing Tflush, not empty records.

[-- Attachment #2: Type: text/html, Size: 1043 bytes --]

  parent reply	other threads:[~2015-08-11 15:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10 14:11 Giacomo Tesio
2015-08-10 14:22 ` erik quanstrom
2015-08-10 14:35   ` Giacomo Tesio
2015-08-10 14:54     ` Charles Forsyth
2015-08-10 15:40       ` Charles Forsyth
2015-08-10 20:17       ` Giacomo Tesio
2015-08-10 20:33         ` Charles Forsyth
2015-08-11 15:48 ` Charles Forsyth [this message]
2015-08-12  0:21   ` Giacomo Tesio
2015-08-12  7:25     ` David du Colombier
2015-08-12  9:18       ` Giacomo Tesio
2015-08-12 17:17         ` 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=CAOw7k5h7o+pCy5TABBtXRgBATqPsRac45_WXttevGzbqLvTg+w@mail.gmail.com \
    --to=charles.forsyth@gmail.com \
    --cc=9fans@9fans.net \
    /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).