From: Mike Galbraith <efault@gmx.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: sysbench+mysql(oltp, readonly) 30% regression with 2.6.26-rc1
Date: Thu, 08 May 2008 11:37:34 +0200 [thread overview]
Message-ID: <1210239454.7036.2.camel@marge.simson.net> (raw)
In-Reply-To: <20080508084607.GA31515@elte.hu>
On Thu, 2008-05-08 at 10:46 +0200, Ingo Molnar wrote:
> Could you perhaps try the hack below that uses /proc/sys/kernel/panic as
> a flag whether the BKL should cause us to block or should be spun upon.
>
> Can you confirm that with that patch too sysbench shows sensitivity to
> the value of the panic flag? [this is the surest way to measure such
> effects as flipping the sysctl only minimally impacts the system.]
Difference for average of 3 runs at 128 clients is 0.3% with this
patch.. iow, nope.
-Mike
next prev parent reply other threads:[~2008-05-08 9:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 4:55 sysbench+mysql(oltp, readonly) 30% regression with 2.6.26-rc1 Zhang, Yanmin
2008-05-07 9:16 ` Ingo Molnar
2008-05-07 9:33 ` Zhang, Yanmin
2008-05-07 10:40 ` Ingo Molnar
2008-05-07 16:26 ` Peter Zijlstra
2008-05-08 6:35 ` Zhang, Yanmin
2008-05-08 8:00 ` Mike Galbraith
2008-05-08 8:46 ` Ingo Molnar
2008-05-08 9:25 ` Ingo Molnar
2008-05-08 10:00 ` Mike Galbraith
2008-05-08 9:37 ` Mike Galbraith [this message]
2008-05-08 9:01 ` Zhang, Yanmin
2008-05-08 9:13 ` Peter Zijlstra
2008-05-08 9:15 ` Mike Galbraith
2008-05-08 9:22 ` Zhang, Yanmin
2008-05-08 9:23 ` Peter Zijlstra
2008-05-09 1:16 ` Zhang, Yanmin
2008-05-09 6:51 ` Peter Zijlstra
2008-05-09 7:32 ` Mike Galbraith
2008-05-09 7:50 ` Peter Zijlstra
2008-05-09 7:58 ` Mike Galbraith
2008-05-09 8:02 ` Peter Zijlstra
2008-05-09 8:23 ` Mike Galbraith
2008-05-09 9:47 ` Mike Galbraith
2008-05-09 7:59 ` Mike Galbraith
2008-05-09 8:10 ` Peter Zijlstra
2008-05-09 8:25 ` Mike Galbraith
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=1210239454.7036.2.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yanmin_zhang@linux.intel.com \
/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