From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Huge TLB performance improvement
Date: Sun, 12 Nov 2006 20:42:58 +0000 [thread overview]
Message-ID: <200611122042.59445.paul@codesourcery.com> (raw)
In-Reply-To: <20061112011035.GB21771@nevyn.them.org>
> A patch which flushes up to 1/32nd of the jump buffer indiscriminately
> cuts it to 1:11-1:13.
>
> Here's that last patch. It changes the hash function so that entries
> from a particular page are always grouped together in tb_jmp_cache,
> then finds the possibly two affected ranges and memsets them clear.
> Thoughts? Is this acceptable, where else should it be tested besides
> MIPS? I haven't fine-tuned the numbers; it currently allows for max 64
> cached jump targets per target page, but that could be made higher or
> lower.
I've applied this patch. It seems a reasonable compromise solution.
I tested a couple of different x86 guests, and couldn't measure any
significant difference in performance.
Paul
prev parent reply other threads:[~2006-11-12 20:43 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
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 [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=200611122042.59445.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 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).