From: Ronald G Minnich <rminnich@lanl.gov>
To: erik quanstrom <quanstro@speakeasy.net>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] hacking issue: memory resizing
Date: Fri, 9 Sep 2005 09:18:59 -0600 [thread overview]
Message-ID: <4321A7E3.1040106@lanl.gov> (raw)
In-Reply-To: <20050909145216.4691A106B2F@dexter-peak.quanstro.net>
erik quanstrom wrote:
> for a toehold on the problem, it looks like the cardbus
> code (/sys/boot/pc/devpccard.c:828) and the functions
> upamalloc() and upafree() in memory.c allow some kernel-level
> dynamic memory. (although upafree() doesn't do anything.)
>
My impression in general is that the device stuff in Plan 9 is not
terribly dynamic -- not surprising, given the time in which the code was
written.
It would be cool if devices could be as dynamic as file systems.
Not an issue in my world, but it's getting to be very important in the
rest of the world, where hotplug is the order of the day, even including
hotplug CPUs and memory at this point. PCMCIA -- that's old news :-)
Anyway, I hope some smart people out there will take this as a challenge
in the kernel space and start thinking about it. Plan 9 is not as
advanced, as some other OSes, in the area of dynamic device management.
ron
next prev parent reply other threads:[~2005-09-09 15:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 15:45 Ronald G Minnich
2005-09-07 15:59 ` Francisco Ballesteros
2005-09-07 18:09 ` Ronald G Minnich
2005-09-08 11:50 ` Dave Lukes
2005-09-08 15:25 ` Ronald G Minnich
2005-09-09 14:52 ` erik quanstrom
2005-09-09 15:18 ` Ronald G Minnich [this message]
2005-09-09 15:31 ` jmk
2005-09-09 18:04 ` erik quanstrom
2005-09-09 18:09 ` jmk
2005-09-09 18:14 ` Eric Van Hensbergen
2005-09-09 19:06 ` Ronald G Minnich
2005-09-09 19:59 ` Tim Newsham
2005-09-09 20:46 ` Francisco Ballesteros
2005-09-10 2:16 ` Brian L. Stuart
2005-09-10 21:41 ` Francisco Ballesteros
2005-09-11 2:11 ` Brian L. Stuart
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=4321A7E3.1040106@lanl.gov \
--to=rminnich@lanl.gov \
--cc=9fans@cse.psu.edu \
--cc=quanstro@speakeasy.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).