All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
To: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-ppc-devel
	<kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	kvm-devel
	<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: the trouble with large pages
Date: Fri, 07 Sep 2007 10:02:53 -0500	[thread overview]
Message-ID: <1189177373.18157.0.camel@squirrel> (raw)
In-Reply-To: <1189176020.9287.18.camel@basalt>

On Fri, 2007-09-07 at 09:40 -0500, Hollis Blanchard wrote:
> The PowerPC 440 Linux kernel uses 256MB pages for the linear mapping.
> When we run that as a guest, those pages would of course need to be
> physically contiguous in the host.
> 
> I think long-term the KVM plan is to move memory allocation out of the
> kernel (where it currently uses vmalloc) into userspace, with the idea
> being that userspace could allocate memory via hugetlbfs. Anybody tried
> hugetlbfs on 440 or e500?
> 
> A poor-man's equivalent might be to limit the host memory to e.g. 256MB,
> then have userspace mmap(/dev/ram) starting there.
> 
> Another possibility is to fake out guest large pages by actually using
> small pages on the host, and handle the extra faults in KVM without
> notifying the guest.

This is what is done on x86.

Regards,

Anthony Liguori



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

      parent reply	other threads:[~2007-09-07 15:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-07 14:40 the trouble with large pages Hollis Blanchard
2007-09-07  4:53 ` Izik Eidus
2007-09-07 15:00 ` Segher Boessenkool
     [not found]   ` <cbb4e3dae13d87254c87d7d6746e4403-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2007-09-07 15:04     ` Anthony Liguori
2007-09-07 15:02 ` Anthony Liguori [this message]

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=1189177373.18157.0.camel@squirrel \
    --to=anthony-rdkfgonbjusknkdkm+me6a@public.gmane.org \
    --cc=hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.