Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp522646ybk; Wed, 13 May 2020 06:21:30 -0700 (PDT) X-Google-Smtp-Source: APiQypJanCePAuPbYa4xYko16zhj+pR1LLGRDA2M/ZwhzNvW2HNkJZO/w4xko3wyZUWrOYKmtOBO X-Received: by 2002:a50:eaca:: with SMTP id u10mr21930905edp.249.1589376090078; Wed, 13 May 2020 06:21:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589376090; cv=none; d=google.com; s=arc-20160816; b=A/Scsa3YY0ZBT/zvHPgH4y6Hf7aULgIoJrpxk1C97Dw4RKUS36DASsKKkbEibGAO9e JtRvkau6tga4RPIjygbMUbw2S9qu9y93N46CVE7urUVNGYBrRoRcaDWHaAw+Vee+hcUL USGuknZXj6tFkK7T2SnbcIeR5IalE82NL/6Yd2iCcfQGi7VX0CHaavJDeyzHTHcrpOop gMP6QaPpM2e9DP94Hc8wLCqxWalJ+Qn/9SpPWbSInkn5c7+ZYgKvlW39PwtRSKZhUobC I01yFmHS/MLpqohLfEyJsrOnQQI+IFxiQziZKqJLpIuAlKc/a/BBIddUk6AFEaGcNqlF EL9g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=+1lnJeUj3FPPM7iZhToV9nshRcJxWMwV+fTUHP7a8RI=; b=Zi3ojTvXDsytSxRkYKQ2r8s8SOyv4MjS7lZ6hf+hg6BKonLWE75x/V3Gf1DO58/lYX g4aK9j+LbcHN3d4cqrcjs+zQnMKeDjuiT1FlCCPcJFTDh7zC9nnvj7woFX+fLBN5uIaY YnsLffrWOHBU5mWonr4BsKwn2ytlQ79CnJHUE5ru34nyCLihUOfNG5rDC5oKooAN7SK4 NnQU0rcT6fSzQ5yIUaVn83mcE77H18a8MuQZTTY2F7hiYxC4+DrgfFuSy5iOsLFeWnWK 9pwMHtodSdLjrQSArvef3p1hmuN+de5M1aFgKz2UCn45DDpKkVJrslYjjd793vHnTtf+ UwPw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=KZYvF7GB; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id gr15si4927015ejb.503.2020.05.13.06.21.06; Wed, 13 May 2020 06:21:30 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=KZYvF7GB; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387752AbgEMNSV (ORCPT + 99 others); Wed, 13 May 2020 09:18:21 -0400 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:34020 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726034AbgEMNSU (ORCPT ); Wed, 13 May 2020 09:18:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1589375898; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=+1lnJeUj3FPPM7iZhToV9nshRcJxWMwV+fTUHP7a8RI=; b=KZYvF7GBIR1L1qalHN5HlJjcSoYOoXjbjqRpaOSHNOo29UsUMMs4juvwxFQrMdMV4z2dv/ 9yyZDmkKd0UpCbEV2cFWGxbVLnl4sLZeofxDvdX2sAU+mh2w/vWZZ4/QLnPYONkoHP3QgK dYwQ1pxCkdd+mnbKjavjsOpOK+0RPts= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-403-r18MYq4kO8Sb_4cWXSv1PA-1; Wed, 13 May 2020 09:18:15 -0400 X-MC-Unique: r18MYq4kO8Sb_4cWXSv1PA-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id B5FA7108BD09; Wed, 13 May 2020 13:18:13 +0000 (UTC) Received: from lorien.usersys.redhat.com (ovpn-113-165.phx2.redhat.com [10.3.113.165]) by smtp.corp.redhat.com (Postfix) with ESMTPS id CB3C45C1C3; Wed, 13 May 2020 13:18:09 +0000 (UTC) Date: Wed, 13 May 2020 09:18:08 -0400 From: Phil Auld To: Vincent Guittot Cc: Ingo Molnar , Peter Zijlstra , Juri Lelli , Dietmar Eggemann , Steven Rostedt , Ben Segall , Mel Gorman , linux-kernel , Tao Zhou , Pavan Kondeti Subject: Re: [PATCH v2] sched/fair: enqueue_task_fair optimization Message-ID: <20200513131808.GG12425@lorien.usersys.redhat.com> References: <20200513123335.28122-1-vincent.guittot@linaro.org> <20200513124540.GB12425@lorien.usersys.redhat.com> <20200513131337.GF12425@lorien.usersys.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 13, 2020 at 03:15:53PM +0200 Vincent Guittot wrote: > On Wed, 13 May 2020 at 15:13, Phil Auld wrote: > > > > On Wed, May 13, 2020 at 03:10:28PM +0200 Vincent Guittot wrote: > > > On Wed, 13 May 2020 at 14:45, Phil Auld wrote: > > > > > > > > Hi Vincent, > > > > > > > > On Wed, May 13, 2020 at 02:33:35PM +0200 Vincent Guittot wrote: > > > > > enqueue_task_fair jumps to enqueue_throttle label when cfs_rq_of(se) is > > > > > throttled which means that se can't be NULL and we can skip the test. > > > > > > > > > > > > > s/be NULL/be non-NULL/ > > > > > > > > I think. > > > > > > This sentence refers to the move of enqueue_throttle and the fact that > > > se can't be null when goto enqueue_throttle and we can jump directly > > > after the if statement, which is now removed in v2 because se is > > > always NULL if we don't use goto enqueue_throttle. > > > > > > I haven't change the commit message for the remove of if statement > > > > > > > Fair enough, it just seems backwards from the intent of the patch now. > > > > There is also an extra } after the update_overutilized_status. > > don't know what I did but it's crap. sorry about that > No worries. I didn't see it when I read it either. The compiler told me :) > Let me prepare a v3 > > > > > > > Cheers, > > Phil > > > > > > > > > > > > > > It's more like if it doesn't jump to the label then se must be NULL for > > > > the loop to terminate. The final loop is a NOP if se is NULL. The check > > > > wasn't protecting that. > > > > > > > > Otherwise still > > > > > > > > > Reviewed-by: Phil Auld > > > > > > > > Cheers, > > > > Phil > > > > > > > > > > > > > Signed-off-by: Vincent Guittot > > > > > --- > > > > > > > > > > v2 changes: > > > > > - Remove useless if statement > > > > > > > > > > kernel/sched/fair.c | 39 ++++++++++++++++++++------------------- > > > > > 1 file changed, 20 insertions(+), 19 deletions(-) > > > > > > > > > > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c > > > > > index a0c690d57430..b51b12d63c39 100644 > > > > > --- a/kernel/sched/fair.c > > > > > +++ b/kernel/sched/fair.c > > > > > @@ -5513,28 +5513,29 @@ enqueue_task_fair(struct rq *rq, struct task_struct *p, int flags) > > > > > list_add_leaf_cfs_rq(cfs_rq); > > > > > } > > > > > > > > > > -enqueue_throttle: > > > > > - if (!se) { > > > > > - add_nr_running(rq, 1); > > > > > - /* > > > > > - * Since new tasks are assigned an initial util_avg equal to > > > > > - * half of the spare capacity of their CPU, tiny tasks have the > > > > > - * ability to cross the overutilized threshold, which will > > > > > - * result in the load balancer ruining all the task placement > > > > > - * done by EAS. As a way to mitigate that effect, do not account > > > > > - * for the first enqueue operation of new tasks during the > > > > > - * overutilized flag detection. > > > > > - * > > > > > - * A better way of solving this problem would be to wait for > > > > > - * the PELT signals of tasks to converge before taking them > > > > > - * into account, but that is not straightforward to implement, > > > > > - * and the following generally works well enough in practice. > > > > > - */ > > > > > - if (flags & ENQUEUE_WAKEUP) > > > > > - update_overutilized_status(rq); > > > > > + /* At this point se is NULL and we are at root level*/ > > > > > + add_nr_running(rq, 1); > > > > > + > > > > > + /* > > > > > + * Since new tasks are assigned an initial util_avg equal to > > > > > + * half of the spare capacity of their CPU, tiny tasks have the > > > > > + * ability to cross the overutilized threshold, which will > > > > > + * result in the load balancer ruining all the task placement > > > > > + * done by EAS. As a way to mitigate that effect, do not account > > > > > + * for the first enqueue operation of new tasks during the > > > > > + * overutilized flag detection. > > > > > + * > > > > > + * A better way of solving this problem would be to wait for > > > > > + * the PELT signals of tasks to converge before taking them > > > > > + * into account, but that is not straightforward to implement, > > > > > + * and the following generally works well enough in practice. > > > > > + */ > > > > > + if (flags & ENQUEUE_WAKEUP) > > > > > + update_overutilized_status(rq); > > > > > > > > > > } > > > > > > > > > > +enqueue_throttle: > > > > > if (cfs_bandwidth_used()) { > > > > > /* > > > > > * When bandwidth control is enabled; the cfs_rq_throttled() > > > > > -- > > > > > 2.17.1 > > > > > > > > > > > > > -- > > > > > > > > > > > -- > > > --