linux-kernel - Re: sched : performance regression 24% between 4.4rc4 and 4.3 kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <566F7715.3020905@redhat.com>
Date:	Mon, 14 Dec 2015 21:12:37 -0500
From:	Rik van Riel <riel@...hat.com>
To:	Jirka Hladky <jhladky@...hat.com>,
	Mike Galbraith <umgwanakikbuti@...il.com>
Cc:	linux-kernel@...r.kernel.org,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: sched : performance regression 24% between 4.4rc4 and 4.3 kernel

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/