From: "boyd, rounin" <boyd@insultant.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Process distribution?
Date: Fri, 21 May 2004 16:27:38 +0200 [thread overview]
Message-ID: <012801c43f3f$c70a7f60$207e7d50@SOMA> (raw)
In-Reply-To: <20040521113733.LDBQ14728.mxfep02.bredband.com@mxfep02>
> Functionality on the CPU servers to stop responding to CPU
> binding requests when they would be overloaded, and accept
> when the load drops.
i think you need virtual cpu servers. cpu <name> binds stuff
to a group of CPUs and they work out the scheduling.
'natch some CPUs have are multiprocessor, eliminating
the process migration problem.
621109-4138
next prev parent reply other threads:[~2004-05-21 14:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 11:37 tt.gustavsson
2004-05-21 13:24 ` a
2004-05-21 14:22 ` Fco.J.Ballesteros
2004-05-21 15:18 ` boyd, rounin
2004-05-21 15:25 ` Fco. J. Ballesteros
2004-05-21 15:29 ` boyd, rounin
2004-05-22 0:54 ` ron minnich
2004-05-21 14:27 ` boyd, rounin [this message]
2004-05-21 22:04 ` Geoff Collyer
2004-05-23 9:33 tt.gustavsson
2004-05-23 13:17 ` a
2004-05-27 4:48 YAMANASHI Takeshi
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='012801c43f3f$c70a7f60$207e7d50@SOMA' \
--to=boyd@insultant.net \
--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).