Linux virtualization list
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Nicholas Mc Guire <der.herr@hofr.at>
Cc: Jens Axboe <jens.axboe@oracle.com>,
	virtualization@lists.linux-foundation.org
Subject: Re: lguest/host benchmarks.
Date: Sat, 09 Jun 2007 20:43:44 +1000	[thread overview]
Message-ID: <1181385825.11961.28.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.60.0706090628570.395@rtl14.hofr.at>

On Sat, 2007-06-09 at 06:44 +0200, Nicholas Mc Guire wrote:
> so the file issue is most likely a memory exhaustion effect on the guest 

Right, I usually run w/ 512M of ram per guest, so I haven't noticed.

> we still are checking things related to the absolute values reported - not 
> yet convinced that timing is that correct on the guest.

It's possible, which is why virtbench runs external to the guest.  I
never trust anyone's non-hardware clocks 8)

> > This can be optimized by enhancing the switcher itself to walk the guest
> > page tables and reflect is straight back into the guest if it's not
> > mapped there.  This shouldn't actually be too hard, but I wonder if it's
> > worth the complexity...
> >
> Even if it were it should not go into lguest - the really nice thing about 
> it is that one can actually understand it !

I agree, but I can probably do this in under 50 lines.  As you say, not
worth it if it doesn't hurt real applications.

Thanks, and thanks for the kind words about lguest!
Rusty.

      reply	other threads:[~2007-06-09 10:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01 15:25 lguest problem on boot of guest kernel Nicholas Mc Guire
2007-06-02 10:27 ` Rusty Russell
2007-06-02 13:24   ` Nicholas Mc Guire
2007-06-08  7:27   ` lguest/host benchmarks Nicholas Mc Guire
2007-06-09  4:16     ` Rusty Russell
2007-06-09  4:27       ` Glauber de Oliveira Costa
2007-06-09  4:28         ` Nicholas Mc Guire
2007-06-09  4:44       ` Nicholas Mc Guire
2007-06-09 10:43         ` Rusty Russell [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=1181385825.11961.28.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=der.herr@hofr.at \
    --cc=jens.axboe@oracle.com \
    --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