Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752660Ab3GICa4 (ORCPT ); Mon, 8 Jul 2013 22:30:56 -0400 Received: from e28smtp08.in.ibm.com ([122.248.162.8]:60173 "EHLO e28smtp08.in.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751792Ab3GICay (ORCPT ); Mon, 8 Jul 2013 22:30:54 -0400 Message-ID: <51DB75D4.6050302@linux.vnet.ibm.com> Date: Tue, 09 Jul 2013 10:30:44 +0800 From: Michael Wang User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1 MIME-Version: 1.0 To: Davidlohr Bueso CC: Peter Zijlstra , Mike Galbraith , LKML , Ingo Molnar , Alex Shi , Namhyung Kim , Paul Turner , Andrew Morton , "Nikunj A. Dadhania" , Ram Pai Subject: Re: [PATCH] sched: smart wake-affine References: <51D29EE5.8080307@linux.vnet.ibm.com> <20130704091339.GK18898@dyad.programming.kicks-ass.net> <51D5428D.7080805@linux.vnet.ibm.com> <1372934013.9046.16.camel@marge.simpson.net> <51D633DB.5010508@linux.vnet.ibm.com> <1372997318.7315.23.camel@marge.simpson.net> <51D64C84.5080100@linux.vnet.ibm.com> <1373002865.8318.11.camel@marge.simpson.net> <51D664B9.7010407@linux.vnet.ibm.com> <1373179405.19316.41.camel@marge.simpson.net> <20130708082106.GW23916@twins.programming.kicks-ass.net> <1373309998.1744.3.camel@buesod1.americas.hpqcorp.net> In-Reply-To: <1373309998.1744.3.camel@buesod1.americas.hpqcorp.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-TM-AS-MML: No X-Content-Scanned: Fidelis XPS MAILER x-cbid: 13070902-2000-0000-0000-00000CCE9CE5 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1109 Lines: 36 Hi, Davidlohr Thanks for the testing :) On 07/09/2013 02:59 AM, Davidlohr Bueso wrote: [snip] >> >> OK, I'll apply the patches, we'll see what happens. If there significant >> fallout we'll immediately have more information anyway ;-) > > So I gave the v2 a spin on my aim7 benchmark on an 80-core 8 socket > DL980. Not much changed, most numbers are in the noise range, however, > with HT off, the high_systime workload suffered in throughput with this > patch with higher concurrency (after 600 users). Image attached. To make sure I'm not on the wrong way... HT here means hyperthreading, correct? I have some questions like: 1. how do you disable the hyperthreading? by manual or some other way? 2. is the 3.10-rc5 in image also disabled the hyperthreading? 3. is the v3 patch set show the same issue? Regards, Michael Wang > > Thanks, > Davidlohr > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/