From: Peter Zijlstra <peterz@infradead.org>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: Rik van Riel <riel@redhat.com>,
Eric Farman <farman@linux.vnet.ibm.com>,
????????? <jinpuwang@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
"KVM-ML (kvm@vger.kernel.org)" <kvm@vger.kernel.org>,
vcaputo@pengaru.com, Matthew Rosato <mjrosato@linux.vnet.ibm.com>
Subject: Re: sysbench throughput degradation in 4.13+
Date: Tue, 3 Oct 2017 10:39:32 +0200 [thread overview]
Message-ID: <20171003083932.3qa7jw2spmi5n5pg@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20171002225312.GA24578@codeblueprint.co.uk>
On Mon, Oct 02, 2017 at 11:53:12PM +0100, Matt Fleming wrote:
> On Wed, 27 Sep, at 01:58:20PM, Rik van Riel wrote:
> >
> > I like the simplicity of your approach! I hope it does not break
> > stuff like netperf...
> >
> > I have been working on the patch below, which is much less optimistic
> > about when to do an affine wakeup than before.
>
> Running netperf for this patch and Peter's patch shows that Peter's
> comes out on top, with scores pretty close to v4.12 in most places on
> my 2-NUMA node 48-CPU Xeon box.
>
> I haven't dug any further into why v4.13-peterz+ is worse than v4.12,
> but I will next week.
So I was waiting for Rik, who promised to run a bunch of NUMA workloads
over the weekend.
The trivial thing regresses a wee bit on the overloaded case, I've not
yet tried to fix it.
next prev parent reply other threads:[~2017-10-03 8:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 14:14 Eric Farman
2017-09-13 8:24 ` 王金浦
2017-09-22 15:03 ` Eric Farman
2017-09-22 15:53 ` Peter Zijlstra
2017-09-22 16:12 ` Eric Farman
2017-09-27 9:35 ` Peter Zijlstra
2017-09-27 16:27 ` Eric Farman
2017-09-28 9:08 ` Christian Borntraeger
2017-09-27 17:58 ` Rik van Riel
2017-09-28 11:04 ` Eric Farman
2017-09-28 12:36 ` Peter Zijlstra
2017-09-28 12:37 ` Peter Zijlstra
2017-10-02 22:53 ` Matt Fleming
2017-10-03 8:39 ` Peter Zijlstra [this message]
2017-10-03 16:02 ` Rik van Riel
2017-10-04 16:18 ` Peter Zijlstra
2017-10-04 18:02 ` Rik van Riel
2017-10-06 10:36 ` Matt Fleming
2017-10-10 14:51 ` Matt Fleming
2017-10-10 15:16 ` Peter Zijlstra
2017-10-10 17:26 ` Ingo Molnar
2017-10-10 17:40 ` Christian Borntraeger
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=20171003083932.3qa7jw2spmi5n5pg@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=borntraeger@de.ibm.com \
--cc=farman@linux.vnet.ibm.com \
--cc=jinpuwang@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@redhat.com \
--cc=mjrosato@linux.vnet.ibm.com \
--cc=riel@redhat.com \
--cc=vcaputo@pengaru.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
all inboxes | Powered by JetHome®