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 14:16:42 +1000 [thread overview]
Message-ID: <1181362602.6025.72.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.60.0706080908100.811@rtl14.hofr.at>
On Fri, 2007-06-08 at 09:27 +0200, Nicholas Mc Guire wrote:
> HI !
Hi Nicholas,
Thanks for this!
> here are some preliminary benchmarks of lguest vs host (2.6.21)
>
> Most results seem resonable - the file create/delete is a bit
> strange - does anybody have an idea why 0k file create/delete could
> be so much faster under lguest and 10k file so much slower ?
Is this ext3? The lguest blockio drvier is very naive and is actually
synchronous (SLOW!), but also ignores barriers.
BTW, I suspect your sh is different inside the guest than host:
> darkstar Lguest 2.6.21 1602 0.21 0.37 2.38 4.02 0.65 1.75 1137 2653 7960
> darkstar Linux 2.6.21 1602 0.18 0.37 3.54 5.20 28.9 0.62 1.59 213. 1042 8725
> The only really serious problem with lguest performance seems to be
> mmap latency, page-faults and protection faults.
Yes. A real page fault hurts quite a bit, because all page faults go
via the host (which can swap out guest pages or have them COW).
Sequence goes:
- Guest userspace hits page
- Trap to switcher
- Switch to host kernel
- Walk guest pagetables to see if it's mapped, it's not, so deliver.
- Switch to guest kernel
- Process fault, insert page table entry
- Trap to switcher
- Switch to host kernel
- Insert page table entry in shadow pagetables
- Switch to guest kernel
- Handle fault
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...
Thanks!
Rusty.
next prev parent reply other threads:[~2007-06-09 4:16 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 [this message]
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
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=1181362602.6025.72.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