From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752621AbcCAIiw (ORCPT ); Tue, 1 Mar 2016 03:38:52 -0500 Received: from mga11.intel.com ([192.55.52.93]:43644 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751984AbcCAIiv (ORCPT ); Tue, 1 Mar 2016 03:38:51 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,522,1449561600"; d="scan'208";a="661685565" From: "Huang\, Ying" To: Ingo Molnar Cc: Peter Zijlstra , Chris Mason , "Peter Zijlstra" , , Sebastian Andrzej Siewior , Davidlohr Bueso , Hugh Dickins , LKML , Linus Torvalds , Mel Gorman , "Thomas Gleixner" , Mel Gorman , Darren Hart , Wu Fengguang Subject: Re: [LKP] [lkp] [futex] 65d8fc777f: +25.6% will-it-scale.per_process_ops References: <871t7vzze1.fsf@yhuang-dev.intel.com> <20160229093708.GA21037@gmail.com> Date: Tue, 01 Mar 2016 16:38:48 +0800 In-Reply-To: <20160229093708.GA21037@gmail.com> (Ingo Molnar's message of "Mon, 29 Feb 2016 10:37:08 +0100") Message-ID: <87si0avbhj.fsf@yhuang-dev.intel.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Ingo, Ingo Molnar writes: > * kernel test robot 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 >