Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752393AbbLBSsf (ORCPT ); Wed, 2 Dec 2015 13:48:35 -0500 Received: from g1t6223.austin.hp.com ([15.73.96.124]:40205 "EHLO g1t6223.austin.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751309AbbLBSsd (ORCPT ); Wed, 2 Dec 2015 13:48:33 -0500 Message-ID: <565F3CFF.8050102@hpe.com> Date: Wed, 02 Dec 2015 13:48:31 -0500 From: Waiman Long User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130109 Thunderbird/10.0.12 MIME-Version: 1.0 To: Peter Zijlstra CC: Ingo Molnar , linux-kernel@vger.kernel.org, Scott J Norton , Douglas Hatch , Paul Turner , Ben Segall , Morten Rasmussen , Yuyang Du Subject: Re: [RFC PATCH 3/3] sched/fair: Use different cachelines for readers and writers of load_avg References: <1448478580-26467-1-git-send-email-Waiman.Long@hpe.com> <1448478580-26467-4-git-send-email-Waiman.Long@hpe.com> <20151130102240.GH17308@twins.programming.kicks-ass.net> <565C9FDC.9020603@hpe.com> <20151130220953.GD3816@twins.programming.kicks-ass.net> <565D1A16.7080105@hpe.com> <20151201084944.GK3816@twins.programming.kicks-ass.net> In-Reply-To: <20151201084944.GK3816@twins.programming.kicks-ass.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1758 Lines: 34 On 12/01/2015 03:49 AM, Peter Zijlstra wrote: > On Mon, Nov 30, 2015 at 10:55:02PM -0500, Waiman Long wrote: >> On 11/30/2015 05:09 PM, Peter Zijlstra wrote: >>> On Mon, Nov 30, 2015 at 02:13:32PM -0500, Waiman Long wrote: >>>>> This begs the question tough; why are you running a global load in a >>>>> cgroup; and do we really need to update this for the root cgroup? It >>>>> seems to me we don't need calc_tg_weight() for the root cgroup, it >>>>> doesn't need to normalize its weight numbers. >>>>> >>>>> That is; isn't this simply a problem we should avoid? >>>> I didn't use any cgroup in my test setup. Autogroup was enabled, though. >>>> Booting up a 4.4-rc2 kernel caused sched_create_group() to be called 56 >>>> times. >>> Yeah, can you kill autogroup and see if that helps? If not, we probably >>> should add some code to avoid calculating things for the root group. >> I will try that out tomorrow. However, SCHED_AUTOGROUP was enabled in the >> distribution kernels. So we still need to look at that with autogroup >> enabled. > Meh, or just tell the people that have stupid large machines to use > noautogroup on boot (its of questionable benefit in the first place imo, > esp. on servers). Yes, I was able to recover most of the lost performance by disabling autogroup. I did send out a new patch to disable load_avg update for root_task_group. I need that for backporting to earlier kernels which was forced to update load_avg for every clock tick even for root_task_group. Cheers, Longman -- 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/