From: Fco.J.Ballesteros <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Process distribution?
Date: Fri, 21 May 2004 16:22:56 +0200 [thread overview]
Message-ID: <818e82f41eaf90756fdf63b4791ddf4b@plan9.escet.urjc.es> (raw)
In-Reply-To: <71b00c64409f2dda50adeea8d576ab4f@9srv.net>
[-- Attachment #1: Type: text/plain, Size: 251 bytes --]
We do something similar for Plan B, and are in the
process of backporting that to Plan 9. See
http://lsub.org/ls/export/bman/4/proc.html
The man page is out of date but that doesn't matter here.
Regarding process migration, please don't, ;-)
[-- Attachment #2: Type: message/rfc822, Size: 3148 bytes --]
From: a@9srv.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Process distribution?
Date: Fri, 21 May 2004 09:24:08 -0400
Message-ID: <71b00c64409f2dda50adeea8d576ab4f@9srv.net>
i suspect a random distribution of processes would yield worse
results than you expect. you really want a scheduler of sorts
that'll find the most appropriate system to run your proc on.
i think the process dispatch stuff you're looking for can all
be done in user mode, with just an app that essentially calls
cpu and does a few namespace ops. the slightly trickier part
(still not *too* hard) is choosing who to dispatch to, but i
think that can be managed properly by having the participating
cpu servers provide their own status information and have a
dispatch daemon on the client poll them when an app needs to
be dispatched. you could even define a way for the app to
specify its resource requirements to the dispatch daemon.
i really should look at the plan 9 and inferno grid stuff.
i forget\0 (and drawterm doesn't work from behind my work
firewall right now): does cpu preserve stdout and stderr?
things get tricky - downright *hard* - when you start
looking for a clean way to do process *migration*.
ア
next prev parent reply other threads:[~2004-05-21 14:22 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 [this message]
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
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=818e82f41eaf90756fdf63b4791ddf4b@plan9.escet.urjc.es \
--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).