All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <levinsasha928@gmail.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: mingo@elte.hu, gorcunov@gmail.com, asias.hejun@gmail.com,
	kvm@vger.kernel.org, ajsween@sandia.gov
Subject: Re: [PATCH] kvm tools: mmap guest kernel instead of reading it into memory
Date: Mon, 12 Dec 2011 19:47:35 +0200	[thread overview]
Message-ID: <1323712055.3269.1.camel@lappy> (raw)
In-Reply-To: <CAOJsxLEyS_DDjcR9b-zFtrh86Pm9KFBXNRzqQahhR5WJUqd2Ng@mail.gmail.com>

On Mon, 2011-12-12 at 16:54 +0200, Pekka Enberg wrote:
> On Mon, Dec 12, 2011 at 4:47 PM, Sasha Levin <levinsasha928@gmail.com> wrote:
> > This patch mmaps guest kernel into it's own memory slot instead of reading
> > it into the memory.
> >
> > The advantages are:
> >  - Smaller memory footprint (same effect as KSM if running multiple guests)
> 
> KSM isn't free so it's smaller footprint with less CPU cycles. It's
> mostly useful for the special case of running tons of guests using the
> same kernel image.

Another usecase which I've only first heard about couple of days ago is
loading extremely large bzImages. Those images are 300MB+ in size and
come with built in filesystem. Apparently it's some sort of a livecd
variant.

-- 

Sasha.


  reply	other threads:[~2011-12-12 15:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12 14:47 [PATCH] kvm tools: mmap guest kernel instead of reading it into memory Sasha Levin
2011-12-12 14:54 ` Pekka Enberg
2011-12-12 17:47   ` Sasha Levin [this message]
2011-12-12 16:40     ` Andrew Walrond
2011-12-12 15:59 ` Pekka Enberg
2011-12-12 18:14   ` Sasha Levin
2011-12-12 18:03     ` Avi Kivity
2011-12-12 17:18 ` Ingo Molnar
2011-12-12 18:08 ` Avi Kivity
2011-12-12 18:10 ` Avi Kivity
2011-12-13  6:46   ` Sasha Levin

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=1323712055.3269.1.camel@lappy \
    --to=levinsasha928@gmail.com \
    --cc=ajsween@sandia.gov \
    --cc=asias.hejun@gmail.com \
    --cc=gorcunov@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@kernel.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.