From: Eric Van Hensbergen <ericvh@gmail.com>
To: erik quanstrom <quanstro@speakeasy.net>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Cc: jmk@plan9.bell-labs.com
Subject: Re: [9fans] hacking issue: memory resizing
Date: Fri, 9 Sep 2005 13:14:18 -0500 [thread overview]
Message-ID: <a4e6962a050909111465e2cea3@mail.gmail.com> (raw)
In-Reply-To: <20050909180402.097CFB0709@conchobor.berzerked.org>
On 9/9/05, erik quanstrom <quanstro@quanstro.net> wrote:
> i guess what i was getting at was: can some of the dynamic bits
> like pccard and usb be flushed out and generalized to support
> general hotplugging, or do we require a new framework?
>
IMHO the right answer is to take a step back and take some time to
think about the "right" way to support hot-pluggable hardware versus
"flushing things out". I'm not saying that we'll need a whole new
framework, but I'd rather design a proper interface versus "patch"
deficiencies.
Some of the Plan B stuff may be pointers in the right direction since
they deal with file servers coming and going on a regular basis. Its
just in the hot-plug case, the file server which is coming and going
is a physical device.
-eric
next prev parent reply other threads:[~2005-09-09 18:14 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
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 [this message]
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=a4e6962a050909111465e2cea3@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=jmk@plan9.bell-labs.com \
--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).