9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Francisco J Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] clunk clunk
Date: Fri,  6 Jan 2006 23:00:41 +0100	[thread overview]
Message-ID: <8ccc8ba40601061400i66078d5es70ff639f0c0ade80@mail.gmail.com> (raw)
In-Reply-To: <13925.1136583282@piper.nectar.cs.cmu.edu>

It works. At least, in the Plan B version, which has just one
worker, it works. It should work with more workers as well.
What happens is that you get more chans waiting to be
clunked into the wait queue. When enough time passes,
and the connection is broken (because of a reboot of
the machine with the server process, or whatever), the queue
will continue to be drained (if there are N workers, you just
would get less draining processes).


On 1/6/06, Dave Eckhardt <davide+p9@cs.cmu.edu> wrote:
> > The code looks at c->dev in cclose to see if the
> > chan is from devmnt.  If so, cclose places the chan on
> > a queue rather than calling devtab[c->dev]->close()
> > and chanfree() directly.  A pool of worker processes
> > tend the queue, like in exportfs, calling close() and
> > chanfree() themselves.
>
> Will that work if there is a cycle with more edges than
> the number of worker processes?
>
> Dave Eckhardt
>
>

      parent reply	other threads:[~2006-01-06 22:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-03 19:28 Bruce Ellis
2006-01-03 19:38 ` Sascha Retzki
2006-01-03 19:46 ` Russ Cox
2006-01-03 20:07   ` Bruce Ellis
2006-01-03 20:24     ` Russ Cox
2006-01-03 21:33       ` Bruce Ellis
2006-01-03 21:47         ` jmk
2006-01-03 22:09           ` Bruce Ellis
2006-01-03 22:14             ` jmk
2006-01-03 22:16               ` Bruce Ellis
2006-01-03 22:36             ` Russ Cox
2006-01-03 22:45               ` Bruce Ellis
2006-01-04 12:15                 ` Russ Cox
2006-01-04 12:25                   ` Bruce Ellis
2006-01-04 15:36                     ` Ronald G Minnich
2006-01-04 15:41                       ` Bruce Ellis
2006-01-05  9:36                     ` Francisco J Ballesteros
2006-01-05  9:39                       ` Russ Cox
2006-01-05 12:00                         ` Bruce Ellis
2006-01-05 12:36                           ` Charles Forsyth
2006-01-05 15:26                           ` Francisco J Ballesteros
2006-01-06 21:34                         ` Dave Eckhardt
2006-01-06 21:57                           ` Bruce Ellis
2006-01-06 22:00                           ` Francisco J Ballesteros [this message]

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=8ccc8ba40601061400i66078d5es70ff639f0c0ade80@mail.gmail.com \
    --to=nemo@lsub.org \
    --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).