From: Huang, Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: [futex] 65d8fc777f: +25.6% will-it-scale.per_process_ops
Date: Tue, 01 Mar 2016 16:38:48 +0800 [thread overview]
Message-ID: <87si0avbhj.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20160229093708.GA21037@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
Hi, Ingo,
Ingo Molnar <mingo@kernel.org> writes:
> * kernel test robot <ying.huang@linux.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
>
WARNING: multiple messages have this Message-ID (diff)
From: "Huang\, Ying" <ying.huang@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>, Chris Mason <clm@fb.com>,
"Peter Zijlstra" <peterz@infradead.org>, <lkp@01.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Davidlohr Bueso <dbueso@suse.de>, Hugh Dickins <hughd@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>,
"Thomas Gleixner" <tglx@linutronix.de>,
Mel Gorman <mgorman@techsingularity.net>,
Darren Hart <dvhart@linux.intel.com>,
Wu Fengguang <fengguang.wu@intel.com>
Subject: Re: [LKP] [lkp] [futex] 65d8fc777f: +25.6% will-it-scale.per_process_ops
Date: Tue, 01 Mar 2016 16:38:48 +0800 [thread overview]
Message-ID: <87si0avbhj.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20160229093708.GA21037@gmail.com> (Ingo Molnar's message of "Mon, 29 Feb 2016 10:37:08 +0100")
Hi, Ingo,
Ingo Molnar <mingo@kernel.org> writes:
> * kernel test robot <ying.huang@linux.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
>
next prev parent reply other threads:[~2016-03-01 8:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 8:36 [futex] 65d8fc777f: +25.6% will-it-scale.per_process_ops kernel test robot
2016-02-29 8:36 ` [lkp] " kernel test robot
2016-02-29 9:37 ` Ingo Molnar
2016-02-29 9:37 ` [lkp] " Ingo Molnar
2016-02-29 17:37 ` Davidlohr Bueso
2016-02-29 17:37 ` [lkp] " Davidlohr Bueso
2016-03-01 8:38 ` Huang, Ying [this message]
2016-03-01 8:38 ` [LKP] " Huang, Ying
2016-03-18 6:12 ` Huang, Ying
2016-03-18 6:12 ` [LKP] [lkp] " Huang, Ying
2016-03-18 8:35 ` Thomas Gleixner
2016-03-18 8:35 ` [LKP] [lkp] " Thomas Gleixner
2016-03-21 2:53 ` Huang, Ying
2016-03-21 2:53 ` [LKP] [lkp] " Huang, Ying
2016-03-21 8:00 ` Thomas Gleixner
2016-03-21 8:00 ` [LKP] [lkp] " Thomas Gleixner
2016-03-21 8:42 ` Huang, Ying
2016-03-21 8:42 ` [LKP] [lkp] " Huang, Ying
2016-03-28 17:14 ` Darren Hart
2016-03-28 17:14 ` [LKP] [lkp] " Darren Hart
2016-03-29 1:12 ` Huang, Ying
2016-03-29 1:12 ` [LKP] [lkp] " Huang, Ying
2016-03-29 5:17 ` Darren Hart
2016-03-29 5:17 ` [LKP] [lkp] " Darren Hart
2016-03-29 5:57 ` Huang, Ying
2016-03-29 5:57 ` [LKP] [lkp] " Huang, Ying
2016-03-29 7:39 ` Peter Zijlstra
2016-03-29 7:39 ` [LKP] [lkp] " Peter Zijlstra
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=87si0avbhj.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=lkp@lists.01.org \
/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.