From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1754519AbcAYBYF (ORCPT <rfc822;w@1wt.eu>);
	Sun, 24 Jan 2016 20:24:05 -0500
Received: from mga14.intel.com ([192.55.52.115]:21792 "EHLO mga14.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753892AbcAYBYE (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Sun, 24 Jan 2016 20:24:04 -0500
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.22,342,1449561600"; 
   d="scan'208";a="867677084"
From: "Huang\, Ying" <ying.huang@intel.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: Waiman Long <Waiman.Long@hp.com>, Peter Zijlstra <peterz@infradead.org>,
        <lkp@01.org>, Will Deacon <will.deacon@arm.com>,
        LKML <linux-kernel@vger.kernel.org>,
        "Paul E. McKenney" <paulmck@us.ibm.com>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Ingo Molnar <mingo@redhat.com>,
        Ding Tianhong <dingtianhong@huawei.com>,
        Thomas Gleixner <tglx@linutronix.de>, fengguang.wu@intel.com,
        Tim Chen <tim.c.chen@linux.intel.com>, Jason Low <jason.low2@hp.com>
Subject: Re: [LKP] [lkp] [locking/mutexes] cb4bbc457b: -40.0% unixbench.score
References: <874me6jql0.fsf@yhuang-dev.intel.com>
	<20160122024801.GA23224@linux-uzut.site>
Date: Mon, 25 Jan 2016 09:23:59 +0800
In-Reply-To: <20160122024801.GA23224@linux-uzut.site> (Davidlohr Bueso's
	message of "Thu, 21 Jan 2016 18:48:01 -0800")
Message-ID: <87io2iih8w.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: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Davidlohr Bueso <dave@stgolabs.net> writes:

> On Fri, 22 Jan 2016, kernel test robot wrote:
>
>>FYI, we noticed the below changes on
>>
>>https://github.com/0day-ci/linux
>> Ding-Tianhong/locking-mutexes-don-t-spin-on-owner-when-wait-list-is-not-NULL/20160121-173317
>>commit cb4bbc457bfed6194ffab1b10c7be73b3f16ca2d ("locking/mutexes: don't spin on owner when wait list is not NULL.")
>
> I'm not sure why this would even be reported, as this patch has not been accepted
> or acked or nothin', by anyone.

Sorry for bothering.  The purpose is FYI as in the original report
email.  We test patches posted to LKML, if we found some changes related
to the patch, we will send out a report.  Hope the reviewer could
take that as information for his/her review if the report isn't totally
nonsense.

> In this particular case that raw performance drop
> is because spinning is pretty much disabled by Ding's change. Totally expected for
> the kind of workload unixbench triggers.

The report is just raw performance data, it still need people to explain
it.  Thanks a lot for your explanation.

> All this does is hurt lkml-searchability.

Sorry, I don't understand this.  You could still search the original
patch.  Could you explain a little?

Best Regards,
Huang, Ying

> Thanks,
> Davidlohr
> _______________________________________________
> LKP mailing list
> LKP@lists.01.org
> https://lists.01.org/mailman/listinfo/lkp