From: Thiemo Seufer <ths@networkno.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Huge TLB performance improvement
Date: Sun, 12 Nov 2006 14:29:38 +0000 [thread overview]
Message-ID: <20061112142938.GC4040@networkno.de> (raw)
In-Reply-To: <200611121408.09895.paul@codesourcery.com>
Paul Brook wrote:
> On Sunday 12 November 2006 11:49, Laurent Desnogues wrote:
> > Daniel Jacobowitz a écrit :
> > > Straight qemu with my previously posted MIPS patches takes 6:13 to
> > > start and reboot a MIPS userspace (through init, so lots of fork/exec).
> > >
> > > Thiemo's patch, which flushes the whole jump buffer, cuts it to 1:40.
> > >
> > > A patch which finds the entries which need to be flushed more
> > > efficiently cuts it to 1:21.
> > >
> > > A patch which flushes up to 1/32nd of the jump buffer indiscriminately
> > > cuts it to 1:11-1:13.
> >
> > Warning: I don't know anything about the Qemu MMU implementation
> > so this question is perhaps stupid :)
> >
> > Did you try to benchmark some user space applications with the
> > various implementations you propose? The boot of a Linux kernel
> > is quite heavy on various kinds of flushes and so is very
> > different from "standard" applications.
>
> MIPS is different because it has a relatively small software managed TLB.
JFTR, increasing the TLB size from 16 to 64 entries made no performance
difference whatsoever.
> Other targets have a hardware managed TLB. On a hardware managed TLB the OS
> treats it as if it were infinite size, and invalidation only occurs when a OS
> changes the mappings. On a software managed TLB "flushes" are more likely to
> occur during normal operation as TLB slots are reused.
The excessive flushing for mips happens because Qemu doesn't properly
model the hardware's ASID handling.
Thiemo
next prev parent reply other threads:[~2006-11-12 14:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 14:59 [Qemu-devel] [PATCH] Huge TLB performance improvement Thiemo Seufer
2006-11-05 15:38 ` Daniel Jacobowitz
2006-11-12 1:10 ` Daniel Jacobowitz
2006-11-12 11:49 ` Laurent Desnogues
2006-11-12 13:52 ` Thiemo Seufer
2006-11-12 14:08 ` Paul Brook
2006-11-12 14:29 ` Thiemo Seufer [this message]
2006-11-12 14:44 ` Paul Brook
2006-11-12 15:07 ` Daniel Jacobowitz
2006-11-12 15:24 ` Daniel Jacobowitz
2006-11-12 15:26 ` Thiemo Seufer
2006-11-12 16:56 ` Daniel Jacobowitz
2006-11-12 17:49 ` Daniel Jacobowitz
2006-11-12 18:02 ` Dirk Behme
2006-11-12 22:13 ` Daniel Jacobowitz
2006-11-12 20:42 ` Paul Brook
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=20061112142938.GC4040@networkno.de \
--to=ths@networkno.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).