From: Peter Zijlstra <peterz@infradead.org>
To: Subhra Mazumdar <subhra.mazumdar@oracle.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
daniel.lezcano@linaro.org, steven.sistare@oracle.com,
dhaval.giani@oracle.com, rohit.k.jain@oracle.com,
Mike Galbraith <umgwanakikbuti@gmail.com>,
Matt Fleming <matt@codeblueprint.co.uk>
Subject: Re: [PATCH 1/3] sched: remove select_idle_core() for scalability
Date: Thu, 31 May 2018 11:26:19 +0200 [thread overview]
Message-ID: <20180531092619.GS12198@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <b2157df2-53d4-79e1-d307-7634fbc844d6@oracle.com>
On Wed, May 30, 2018 at 03:08:21PM -0700, Subhra Mazumdar wrote:
> I tested with FOLD+AGE+ONCE+PONIES+PONIES2 shift=0 vs baseline but see some
> regression for hackbench and uperf:
I'm not seeing a hackbench regression myself, but I let it run a whole
lot of stuff over-night and I do indeed see some pain points, including
sysbench-mysql and some schbench results.
> I have a patch which is much smaller but seems to work well so far for both
> x86 and SPARC across benchmarks I have run so far. It keeps the idle cpu
> search between 1 core and 2 core amount of cpus and also puts a new
> sched feature of doing idle core search or not. It can be on by default but
> for workloads (like Oracle DB on x86) we can turn it off. I plan to send
> that after some more testing.
Sure thing..
next prev parent reply other threads:[~2018-05-31 9:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 0:41 [RFC/RFT PATCH 0/3] Improve scheduler scalability for fast path subhra mazumdar
2018-04-24 0:41 ` [PATCH 1/3] sched: remove select_idle_core() for scalability subhra mazumdar
2018-04-24 12:46 ` Peter Zijlstra
2018-04-24 21:45 ` Subhra Mazumdar
2018-04-25 17:49 ` Peter Zijlstra
2018-04-30 23:38 ` Subhra Mazumdar
2018-05-01 18:03 ` Peter Zijlstra
2018-05-02 21:58 ` Subhra Mazumdar
2018-05-04 18:51 ` Subhra Mazumdar
2018-05-29 21:36 ` Peter Zijlstra
2018-05-30 22:08 ` Subhra Mazumdar
2018-05-31 9:26 ` Peter Zijlstra [this message]
2018-04-24 0:41 ` [PATCH 2/3] sched: introduce per-cpu var next_cpu to track search limit subhra mazumdar
2018-04-24 12:47 ` Peter Zijlstra
2018-04-24 22:39 ` Subhra Mazumdar
2018-04-24 0:41 ` [PATCH 3/3] sched: limit cpu search and rotate search window for scalability subhra mazumdar
2018-04-24 12:48 ` Peter Zijlstra
2018-04-24 22:43 ` Subhra Mazumdar
2018-04-24 12:48 ` Peter Zijlstra
2018-04-24 22:48 ` Subhra Mazumdar
2018-04-24 12:53 ` Peter Zijlstra
2018-04-25 0:10 ` Subhra Mazumdar
2018-04-25 15:36 ` Peter Zijlstra
2018-04-25 18:01 ` Peter Zijlstra
2018-05-04 2:46 ` [lkp-robot] [sched] 9824134a55: hackbench.throughput +85.7% improvement kernel test robot
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=20180531092619.GS12198@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=daniel.lezcano@linaro.org \
--cc=dhaval.giani@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@redhat.com \
--cc=rohit.k.jain@oracle.com \
--cc=steven.sistare@oracle.com \
--cc=subhra.mazumdar@oracle.com \
--cc=umgwanakikbuti@gmail.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 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.