linux-kernel - Re: [LKP] [lkp] [futex] 65d8fc777f: +25.6% will-it-scale.per_process

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87si0avbhj.fsf@yhuang-dev.intel.com>
Date:	Tue, 01 Mar 2016 16:38:48 +0800
From:	"Huang\, Ying" <ying.huang@...el.com>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>, Chris Mason <clm@...com>,
	"Peter Zijlstra" <peterz@...radead.org>, <lkp@...org>,
	Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
	Davidlohr Bueso <dbueso@...e.de>,
	Hugh Dickins <hughd@...gle.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Mel Gorman <mgorman@...e.de>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	Mel Gorman <mgorman@...hsingularity.net>,
	Darren Hart <dvhart@...ux.intel.com>,
	Wu Fengguang <fengguang.wu@...el.com>
Subject: Re: [LKP] [lkp] [futex] 65d8fc777f: +25.6% will-it-scale.per_process_ops

Hi, Ingo,

Ingo Molnar <mingo@...nel.org> writes:

> * kernel test robot <ying.huang@...ux.intel.com> wrote:
>
>> FYI, we noticed the below changes on
>> 
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master 
>> commit 65d8fc777f6dcfee12785c057a6b57f679641c90 ("futex: Remove requirement for 
>> lock_page() in get_futex_key()")
>
> I have asked for this before, but let me try again: could you _PLEASE_ make these 
> emails more readable?
>
> For example what are the 'below changes'? Changes in the profile output? Profiles 
> always change from run to run, so that alone is not informative.
>
> Also, there are a lot of changes - which ones prompted the email to be generated?
>
> All in one, this email is hard to parse, because it just dumps a lot of 
> information with very little explanatory structure for someone not versed in their 
> format. Please try to create an easy to parse 'story' that leads the reader 
> towards what you want these emails to tell - not just a raw dump of seemingly 
> unconnected pieces of data ...

Your input are valuable for us.  We are discussing how to improve our
reporting to be helpful for kernel developers.  Will go back to you soon
on this.

Best Regards,
Huang, Ying

> Thanks,
>
> 	Ingo
>