From: Rik van Riel <riel@redhat.com>
To: Jirka Hladky <jhladky@redhat.com>,
Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: sched : performance regression 24% between 4.4rc4 and 4.3 kernel
Date: Mon, 14 Dec 2015 21:12:37 -0500 [thread overview]
Message-ID: <566F7715.3020905@redhat.com> (raw)
In-Reply-To: <CAE4VaGCgAvvQXDsv=Gn8B0JtTzCnXe0oP63HLQWSCyY_QNOB7g@mail.gmail.com>
On 12/14/2015 06:52 PM, Jirka Hladky wrote:
> Hi all,
>
> I have the results of bisecting:
>
> first bad commit: [973759c80db96ed4b4c5cb85ac7d48107f801371] Merge tag
> 'v4.3-rc1' into sched/core, to refresh the branch
>
> Could you please have a look at this commit why it has caused the
> performance regression when running 4 stream benchmarks in parallel on 4
> NUMA node server?
That is a merge commit. It contains no actual code changes.
> Please let me know if you need additional data. git bisect log is bellow.
It looks like "git bisect" may have led you astray.
I am not sure what debugging tool to use to figure out which
of the patches from some merged-in branch caused the issue,
but hopefully one of the people reading this email know a trick.
--
All rights reversed
next prev parent reply other threads:[~2015-12-15 2:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 14:17 sched : performance regression 24% between 4.4rc4 and 4.3 kernel Jirka Hladky
2015-12-12 7:04 ` Mike Galbraith
2015-12-12 14:16 ` Jirka Hladky
2015-12-12 14:37 ` Mike Galbraith
2015-12-15 0:02 ` Jirka Hladky
2015-12-15 0:04 ` Jirka Hladky
[not found] ` <CAE4VaGCgAvvQXDsv=Gn8B0JtTzCnXe0oP63HLQWSCyY_QNOB7g@mail.gmail.com>
2015-12-15 2:12 ` Rik van Riel [this message]
2015-12-15 8:49 ` Jirka Hladky
2015-12-16 12:56 ` Jirka Hladky
2015-12-16 13:50 ` Peter Zijlstra
2015-12-16 17:04 ` Jirka Hladky
[not found] ` <CAE4VaGD49UAsBJn3jgg0kREWqjYz8UnvWOi8zU4d5HgNgNS-sQ@mail.gmail.com>
2015-12-17 15:43 ` Jirka Hladky
2015-12-18 2:49 ` 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=566F7715.3020905@redhat.com \
--to=riel@redhat.com \
--cc=jhladky@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--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 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).