9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: EBo <ebo@sandien.com>
To: <9fans@9fans.net>
Subject: Re: [9fans] 9ttp
Date: Thu,  8 Sep 2011 12:28:58 -0500	[thread overview]
Message-ID: <8a566d6213ccc61e0b989514563fd8c1@swcp.com> (raw)
In-Reply-To: <e81467881962f75936ad576810884410@coraid.com>

 On Thu, 8 Sep 2011 10:18:16 -0700, David Leimbach wrote:
> On Thu, Sep 8, 2011 at 9:59 AM, ron minnich <rminnich@gmail.com>
> wrote:
>
>> On Thu, Sep 8, 2011 at 9:56 AM, John Floren <john@jfloren.net>
>> wrote:
>>
>> > I do not think it is acceptable to have to fork repeatedly merely
>> to
>> > efficiently read a file. Also, as far as I can tell, exactly one
>> > program (fcp) does that.
>> >
>> > Can a single process have multiple outstanding requests? My
>> > investigations indicated not, but then again I may have mis-read
>> > things.
>>
>> So, John, you don't think it's reasonable to rewrite every program a
>> la fcp? How unreasonable of you :-)
>
> "Perhaps if we built a large wooden badger..."

 On Thu, 8 Sep 2011 13:20:37 -0400, erik quanstrom wrote:
>
> alternatively, the mount driver could be rewritten.

 coconuts?

   EBo --




  reply	other threads:[~2011-09-08 17:28 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08  8:36 s s
2011-09-08  8:51 ` hiro
2011-09-08 16:21   ` David Leimbach
2011-09-08  9:09 ` dexen deVries
2011-09-08  9:17   ` Steve Simon
2011-09-08  9:22   ` dexen deVries
2011-09-08 12:34     ` hiro
     [not found] ` <CAFSF3XN_NcKfMzugkhoj2CTaBF6Gfdke0XstEjPqcjr9FswpPw@mail.gmail.c>
2011-09-08 12:54   ` erik quanstrom
2011-09-08 13:04     ` dexen deVries
2011-09-08 16:24       ` David Leimbach
     [not found]       ` <CAJJ04x7xC4iuqm0HOzKN-Jb3FSmg8w1E+1Lc06pYaOm_diBNsQ@mail.gmail.c>
2011-09-08 16:31         ` erik quanstrom
2011-09-08 16:56           ` John Floren
2011-09-08 16:59             ` ron minnich
2011-09-08 17:18               ` David Leimbach
     [not found]             ` <CAP6exYJSScKcavDvR55KqJyG5-GphLQxV_+-WuwzgU3CH0pV8w@mail.gmail.c>
2011-09-08 17:20               ` erik quanstrom
2011-09-08 17:28                 ` EBo [this message]
2011-09-08 19:44             ` Bakul Shah
2011-09-08 20:14               ` John Floren
2011-09-08 20:35                 ` Bakul Shah
2011-09-08 20:43                   ` Francisco J Ballesteros
2011-09-08 22:49                     ` Bruce Ellis
2011-09-08 23:19                       ` Venkatesh Srinivas
2011-09-08 23:29                         ` ron minnich
2011-09-08 23:48                           ` Venkatesh Srinivas
2011-09-09  0:18                       ` Eric Van Hensbergen
     [not found]                   ` <CAP6exYKARAZWWWXfK6myj+y47k3XmNnyF4z17zuHOZHczxDOhw@mail.gmail.c>
2011-09-08 23:32                     ` erik quanstrom
2011-09-08 23:51                       ` Venkatesh Srinivas
2011-09-09  8:13                         ` Charles Forsyth
2011-09-09  9:26                           ` Bruce Ellis
2011-09-09  9:36                             ` dexen deVries
2011-09-09 11:26                               ` Bruce Ellis
2011-09-08 20:18               ` erik quanstrom

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=8a566d6213ccc61e0b989514563fd8c1@swcp.com \
    --to=ebo@sandien.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).