From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: IO_MEM_NB_ENTRIES limit
Date: Sun, 11 May 2008 19:45:09 +0100 [thread overview]
Message-ID: <200805111945.10204.paul@codesourcery.com> (raw)
In-Reply-To: <48273023.2010808@bellard.org>
On Sunday 11 May 2008, Fabrice Bellard wrote:
> andrzej zaborowski wrote:
> > [...]
> > Here are some benchmark results:
>
> Benchmarks measuring the boot time mainly measure the dynamic
> translation time, so they are not much meaningful. It would be better to
> launch say nbench or a compilation with gcc.
Once you hit userspace (particularly things like udev) you do a lot of TLB
thrashing, which can show interesting things about the TLB invalidation/slow
path performance.
I agree things like nbench tend to be a good test of the TLB fast path.
Paul
prev parent reply other threads:[~2008-05-11 18:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 11:35 [Qemu-devel] IO_MEM_NB_ENTRIES limit andrzej zaborowski
2008-05-11 15:20 ` [Qemu-devel] " andrzej zaborowski
2008-05-11 15:25 ` Fabrice Bellard
2008-05-11 15:59 ` Fabrice Bellard
2008-05-11 17:18 ` andrzej zaborowski
2008-05-11 17:39 ` Fabrice Bellard
2008-05-11 17:42 ` Fabrice Bellard
2008-05-11 18:45 ` Paul Brook [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=200805111945.10204.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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.