9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Francisco Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] hacking issue: memory resizing
Date: Wed,  7 Sep 2005 17:59:22 +0200	[thread overview]
Message-ID: <600308d605090708597bc20a20@mail.gmail.com> (raw)
In-Reply-To: <431F0B19.9030400@lanl.gov>

Getting bigger should be easy, probably just populating
the allocators, perhaps using extra rmaps for the
extra mem and doing something similar with the allocators on top.

Getting smaller may require assigning pages  first from permanent
rmaps, to avoid relocating vm to the permanent ones.
But, is this part really needed?


On 9/7/05, Ronald G Minnich <rminnich@lanl.gov> wrote:
> anybody willing to think about whether dynamic memory resizing would be
> doable in a Plan 9 kernel? This is both get bigger and get smaller.
> 
> newer machines have hot-plug memory, as do virtual machines.
> 
> ron
>


  reply	other threads:[~2005-09-07 15:59 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 [this message]
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
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=600308d605090708597bc20a20@mail.gmail.com \
    --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).