From: Arnd Bergmann <arnd@arndb.de>
To: Mark Williamson <maw48@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Luke Kenneth Casson Leighton <lkcl@lkcl.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] Re: [XEN] using shmfs for swapspace
Date: Wed, 5 Jan 2005 01:11:54 +0100 [thread overview]
Message-ID: <200501050111.59072.arnd@arndb.de> (raw)
In-Reply-To: <200501040304.10128.maw48@cl.cam.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 1978 bytes --]
On Dinsdag 04 Januar 2005 04:04, Mark Williamson wrote:
> > for doing opportunistic page recycling ("I dont need this page but when
> > I ask for it back please tell me if you trashed the content")
>
> We've talked about doing this but AFAIK nobody has gotten round to it yet
> because there hasn't been a pressing need (IIRC, it was on the todo list when
> Xen 1.0 came out).
>
> IMHO, it doesn't look terribly difficult but would require (hopefully small)
> modifications to the architecture independent code, plus a little bit of
> support code in Xen.
>
> I'd quite like to look at this one fine day but I suspect there are more
> useful things I should do first...
There are two other alternatives that are already used on s390 for making
multi-level paging a little more pleasant:
- Pseudo faults: When Linux accesses a page that it believes to be present
but is actually swapped out in z/VM, the VM hypervisor causes a special
PFAULT exception. Linux can then choose to either ignore this exception
and continue, which will force VM to swap the page back in. Or it can
do a task switch and wait for the page to come back. At the point where
VM has read the page back from its swap device, it causes another
exception, after which Linux wakes up the sleeping process.
see arch/s390/mm/fault.c
- Ballooning:
z/VM has an interface (DIAG 10) for the OS to tell it about a page that
is currently unused. The kernel uses get_free_page to reserve a number
of pages, then calls DIAG10 to give it to z/VM. The amount of pages to
give back to the hypervisor is determined by a system wide workload
manager.
see arch/s390/mm/cmm.c
When you want to introduce some interface in Xen, you probably want
something more powerful than these, but it probably makes sense to
see them as a base line of what can be done with practically no
common code changes (if you don't do similar stuff already).
Arnd <><
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-05 0:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-02 16:26 [XEN] using shmfs for swapspace Luke Kenneth Casson Leighton
2005-01-03 18:31 ` Joseph Fannin
2005-01-03 20:53 ` Luke Kenneth Casson Leighton
2005-01-03 21:06 ` Alan Cox
2005-01-04 3:04 ` [Xen-devel] " Mark Williamson
2005-01-04 14:05 ` Rik van Riel
2005-01-06 11:38 ` Luke Kenneth Casson Leighton
2005-01-05 0:11 ` Arnd Bergmann [this message]
2005-01-21 21:37 ` Rik van Riel
2005-01-26 20:56 ` Mark Williamson
2005-01-27 10:33 ` Nuutti Kotivuori
2005-01-03 21:07 ` Adam Heath
2005-01-04 9:30 ` Luke Kenneth Casson Leighton
2005-01-04 14:06 ` Rik van Riel
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=200501050111.59072.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcl@lkcl.net \
--cc=maw48@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.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