public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Marcelo Tosatti <marcelo@kvack.org>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
	Avi Kivity <avi@qumranet.com>
Subject: Re: [PATCH] QEMU/KVM: large page support
Date: Sat, 23 Feb 2008 16:56:12 -0600	[thread overview]
Message-ID: <47C0A48C.20802@codemonkey.ws> (raw)
In-Reply-To: <20080223225407.GA8465@dmt>

Marcelo Tosatti wrote:
> I thought about doing that (gets rid of the 4GB+ special casing) but we
> lose the ability to compact smaller allocations in a single largepage.
>
> Right now the VGA BIOS and the BIOS fit in the same largepage, for
> example.
>   

Ah, good point.  I was actually talking about doing this adjustment for 
ram regardless of whether we're using large pages--not necessarily for 
all memory allocations.  I saw no harm in doing this alignment even if 
we were using tmpfs and just getting 4k pages.  Of course, I think we're 
in agreement here though :-)

> I like the idea. I'll change "-hugetlb-path" to "-mem-path" for now (and
> test it with tmpfs). Not so fond of hardcoding a path in QEMU though.
>   

If we had a unified tmpfs/hugetlbfs, I think it would make a lot of 
sense.  I think I need to ask around though first and see how reasonable 
that is.

Regards,

Anthony Liguori


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

      reply	other threads:[~2008-02-23 22:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-23 14:48 [PATCH] QEMU/KVM: large page support Marcelo Tosatti
2008-02-23 18:29 ` Anthony Liguori
2008-02-23 22:54   ` Marcelo Tosatti
2008-02-23 22:56     ` 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=47C0A48C.20802@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=marcelo@kvack.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