From: Andrea Arcangeli <andrea@qumranet.com>
To: Farkas Levente <lfarkas@bppiac.hu>
Cc: "David S. Ahern" <daahern@cisco.com>, kvm@vger.kernel.org
Subject: Re: Benchmarking on CentOS 5
Date: Sun, 1 Jun 2008 16:32:59 +0200 [thread overview]
Message-ID: <20080601143259.GE28289@duo.random> (raw)
In-Reply-To: <484039C1.2010806@bppiac.hu>
On Fri, May 30, 2008 at 07:30:41PM +0200, Farkas Levente wrote:
> without crash) and the performance is similar (ie 80-90%) to the
> development version. unfortunately it seems currently there is no such
I hope you didn't reach this conclusion about different performance
between enterprise kernel host and mainline kernel host because I
didn't answer promptly to your previous email, sorry!
With regard to your performance question, preempt notifier emulation
really shouldn't be noticeable in real life. It worth to run the
fastest code only if you're doing pure benchmarking, in which case you
want to avoid any unnecessary exception and heavyweight exit (that
should reduces the time to schedule of a couple thousand cycles I
guess, but re-schedule events aren't so frequent and this is a
per-task per-cpu breakpoint with my latest emulation logic taking
advantage of the __switch_to internals).
I can hardly measure any difference here between SLES10 SP2 host and
mainline host with a simple dd from pagecache to /dev/null. The change
between enterprise kernel and current mainline kernel may be more
significant for the final performance than the impact of the preempt
notifier emulation. In any case the difference should be much less
than 5% as far as preempt notifier emulation is concerned. It should
be couple usec lost every couple msec or so.
next prev parent reply other threads:[~2008-06-01 14:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 17:48 Benchmarking on CentOS 5 Cam Macdonell
2008-05-28 18:33 ` Andrea Arcangeli
2008-05-28 20:27 ` Farkas Levente
2008-05-29 9:23 ` Andrea Arcangeli
2008-05-29 10:13 ` Farkas Levente
[not found] ` <483F75CC.9010303@cisco.com>
[not found] ` <ac75d95a0805300601x4e8b7400sf03280c80813b09e@mail.gmail.com>
[not found] ` <48400371.3060208@cisco.com>
2008-05-30 17:30 ` Farkas Levente
2008-06-01 14:32 ` Andrea Arcangeli [this message]
2008-06-02 9:05 ` Amit Shah
2008-06-02 15:56 ` Dor Laor
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=20080601143259.GE28289@duo.random \
--to=andrea@qumranet.com \
--cc=daahern@cisco.com \
--cc=kvm@vger.kernel.org \
--cc=lfarkas@bppiac.hu \
/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