From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] plan 9 overcommits memory?
Date: Fri, 7 Sep 2007 14:09:44 +1000 [thread overview]
Message-ID: <775b8d190709062109o1c0a64b8y55ceb79e95083ecb@mail.gmail.com> (raw)
In-Reply-To: <1189134549.6197.2.camel@ginkgo>
this thread is now twice as big as the swap and proc code.
is it really that much fun to do research this way?
yes, it has been done. no, my current work has nothing
to do with this issue.
someone written a line of relevant code during this "discussion"?
brucee
On 9/7/07, Roman Shaposhnik <rvs@sun.com> wrote:
> On Thu, 2007-09-06 at 12:38 -0700, ron minnich wrote:
> > On 9/6/07, Joel C. Salomon <joelcsalomon@gmail.com> wrote:
> >
> > > I can't imagine that either of these uses are nearly compelling enough
> > > to open this can of worms.... Has anyone truly felt confined by Plan
> > > 9's fork+exec model?
> >
> > yes, because exec takes a pathname. that's a pull model. That is
> > pretty awful in a large machine. Define awful: ok, it's the difference
> > between startup times of 3+ minutes, 400 nodes, vs. 3 seconds. That's
> > awful.
> >
> > it's why we started doing xcpu in the first place: push the binary to
> > a ram disk, then at least xcpu is pulling from a local place, not a
> > network. But xcpu was a compromise: I really wanted to do a process
> > creation device.
>
> Exposing an interface for process manipulation to userspace would be
> quite cool. Any prototypes on Plan9 so far?
>
> Thanks,
> Roman.
>
>
next prev parent reply other threads:[~2007-09-07 4:09 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-03 3:38 geoff
2007-09-03 5:35 ` Scott Schwartz
2007-09-03 6:05 ` Uriel
2007-09-03 13:33 ` erik quanstrom
2007-09-03 17:09 ` john
2007-09-03 17:17 ` Gorka Guardiola
2007-09-03 17:25 ` Francisco J Ballesteros
2007-09-03 17:30 ` john
2007-09-03 19:47 ` Charles Forsyth
2007-09-03 19:46 ` Uriel
2007-09-03 19:54 ` Charles Forsyth
2007-09-03 19:54 ` Uriel
2007-09-03 20:34 ` geoff
2007-09-03 20:16 ` erik quanstrom
2007-09-03 17:32 ` erik quanstrom
2007-09-03 17:39 ` Francisco J Ballesteros
2007-09-03 17:43 ` john
2007-09-03 17:45 ` john
2007-09-03 19:52 ` Charles Forsyth
2007-09-05 8:33 ` sqweek
2007-09-04 8:48 ` Douglas A. Gwyn
2007-09-03 18:13 ` geoff
2007-09-03 20:17 ` erik quanstrom
2007-09-03 20:48 ` geoff
2007-09-03 22:01 ` erik quanstrom
2007-09-03 22:43 ` Charles Forsyth
2007-09-03 23:51 ` erik quanstrom
2007-09-04 0:04 ` Charles Forsyth
2007-09-04 14:44 ` erik quanstrom
2007-09-04 15:07 ` Charles Forsyth
2007-09-04 15:18 ` ron minnich
2007-09-04 15:18 ` Charles Forsyth
2007-09-05 8:48 ` Douglas A. Gwyn
2007-09-05 10:53 ` erik quanstrom
2007-09-06 8:42 ` Douglas A. Gwyn
2007-09-06 17:15 ` Joel C. Salomon
2007-09-06 19:38 ` ron minnich
2007-09-06 20:18 ` Charles Forsyth
2007-09-06 23:37 ` Steve Simon
2007-09-07 3:09 ` Roman Shaposhnik
2007-09-07 4:09 ` Bruce Ellis [this message]
2007-09-07 4:25 ` Lyndon Nerenberg
2007-09-07 4:37 ` Bruce Ellis
2007-09-07 4:43 ` Lyndon Nerenberg
2007-09-10 15:24 ` roger peppe
2007-09-07 10:55 ` erik quanstrom
2007-09-04 23:32 ` erik quanstrom
2007-09-03 21:16 ` Charles Forsyth
2007-09-03 21:19 ` ron minnich
2007-09-03 21:41 ` Eric Van Hensbergen
2007-09-03 21:51 ` erik quanstrom
2007-09-03 13:21 ` erik quanstrom
2007-09-03 14:01 ` Sape Mullender
2007-09-03 14:32 ` erik quanstrom
2007-09-03 15:28 ` Sape Mullender
2007-09-04 4:32 ` lucio
2007-09-04 7:23 ` Dave Eckhardt
2007-09-04 8:48 ` Douglas A. Gwyn
-- strict thread matches above, loose matches on Subject: below --
2007-08-31 11:41 erik quanstrom
2007-09-02 21:27 ` Russ Cox
2007-09-03 0:43 ` erik quanstrom
2007-09-04 8:47 ` Douglas A. Gwyn
2007-09-04 13:39 ` David Leimbach
2007-09-04 14:41 ` erik quanstrom
2007-09-04 15:54 ` David Leimbach
2007-09-04 17:37 ` sqweek
2007-09-04 18:10 ` ron minnich
2007-09-04 18:53 ` sqweek
2007-09-03 1:23 ` Scott Schwartz
2007-09-03 1:47 ` ron minnich
2007-09-03 2:11 ` erik quanstrom
2007-09-03 2:11 ` erik quanstrom
2007-09-04 8:48 ` Douglas A. Gwyn
2007-09-03 5:28 ` Scott Schwartz
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=775b8d190709062109o1c0a64b8y55ceb79e95083ecb@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--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).