From: Peter Chubb <peterc@gelato.unsw.edu.au>
To: carsteno@de.ibm.com
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
linux-mm@kvack.org, Peter Chubb <peterc@gelato.unsw.edu.au>,
virtualization@lists.linux-foundation.org
Subject: Re: RFC: multiple address spaces for one process
Date: Sat, 30 Jun 2007 05:59:07 -0400 [thread overview]
Message-ID: <87d4zdix04.wl%peter@chubb.wattle.id.au> (raw)
In-Reply-To: <4685D9C9.20504@de.ibm.com>
In LinuxOnLinux, the guest is just another linux process (or
rather, one per virtual CPU). So what this patch does is allow such a
garden-variety process to have more than one address space and switch
between them.2
Essentially what I'm doing is treating the standard linux VM as a huge
software-loaded TLB. When the guest gets a TLB miss, the VMM calls
mmap() to insert the translation. Without the patch the address
space has to be remapped on every guest context switch. The patch
adds address-space IDs to make that unnecessary.
What I'm wondering is if there are any *other* uses for this (not just
virtualisation). I know qemu uses mmap() to create its address
spaces if CONFIG_SOFTMMU is not defined, and could thus benefit.
--
Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au
http://www.ertos.nicta.com.au ERTOS within National ICT Australia
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-06-30 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 11:08 Peter Chubb
2007-06-29 14:32 ` Jeremy Fitzhardinge
2007-06-30 4:19 ` Carsten Otte
2007-06-30 9:59 ` Peter Chubb [this message]
2007-06-30 16:30 ` Jeremy Fitzhardinge
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=87d4zdix04.wl%peter@chubb.wattle.id.au \
--to=peterc@gelato.unsw.edu.au \
--cc=carsteno@de.ibm.com \
--cc=jeremy@goop.org \
--cc=linux-mm@kvack.org \
--cc=virtualization@lists.linux-foundation.org \
/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