Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp1191083ybl; Fri, 16 Aug 2019 10:22:00 -0700 (PDT) X-Google-Smtp-Source: APXvYqy2Hl9klygVVF0qI1fZnqZUsWs+Se2V3avrX6xmkW5FXIuhZho420Q3AHYGO4WlNBIY2Oc0 X-Received: by 2002:a65:6216:: with SMTP id d22mr8109644pgv.404.1565976120359; Fri, 16 Aug 2019 10:22:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565976120; cv=none; d=google.com; s=arc-20160816; b=JaAFa+u+fEYTDg5NPEcZvhQNIjxsp9237iMgQMROZczgtlFWAgjD+RkBZHIHPRuA6h Kp7efUONAqUHMzojFLzvDBKOHo8xRKtxk2LQkDJmc5ahq1CNapn14boB/HMeuCka+MiO L6tStdEeeqZfjXaAZ/43ALxQ1p2Ju69BV9Wn8AbvoV71JyLrzjS8TORqZE0mbXBr26gL v+YeokSa0dtCZ/Gl/FKyNT14Nsqpk9w6vA8mvIKtAtAqwGF7RUP+rxNQXP4/gcIRyoTz MAqY79dTwX/NhIDlmNrdewZHuxtzkB6oLmiOKy2gsC1N2yAXPp5FA7OJZjLCpwQ2o4lT aDKQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=gQXM+EsqZAYoX2047rvV5pbRn4+bCDPcp1turXt7cpM=; b=wt3FTXcpYXiPgVC7hJi/gqyrVm0+4i1nsoVCUmZCzKfBRp1dMsO+DKnNBoB2aZVbVW /CIU930HgOYSCyWLHYsqakDFHaxK7pDwX5g3l71lDo5/KgNLEI7UR89/lOlM7KKcehf2 kHROR0bPO3+av/OVKYbaA+4CejVzjl2HYF9urAoJmzIap39TbzEzWo9QCXPc+qk9i0u9 VEQN0RSs8im7oaPQnpzJ4/iVYizXr6xTKQo+1qsXjacJWS7EUAHVDOAA+uvp/Fu18X5N MZf1YZiWrM1/oEY5/iGYDeP5CPF0vX6nPNLQusU0Zq9I1d+ad2KFOGKgkVdVZxe6LXZ1 XPeQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p14si4349544plo.119.2019.08.16.10.21.45; Fri, 16 Aug 2019 10:22:00 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727555AbfHPRTo (ORCPT + 99 others); Fri, 16 Aug 2019 13:19:44 -0400 Received: from foss.arm.com ([217.140.110.172]:59274 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726943AbfHPRTn (ORCPT ); Fri, 16 Aug 2019 13:19:43 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 271DA28; Fri, 16 Aug 2019 10:19:43 -0700 (PDT) Received: from [10.1.194.37] (e113632-lin.cambridge.arm.com [10.1.194.37]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 281F63F694; Fri, 16 Aug 2019 10:19:42 -0700 (PDT) Subject: Re: [PATCH] sched/fair: don't assign runtime for throttled cfs_rq To: Liangyan Cc: Ingo Molnar , Peter Zijlstra , linux-kernel@vger.kernel.org, shanpeic@linux.alibaba.com, xlpang@linux.alibaba.com, pjt@google.com References: <20190814180021.165389-1-liangyan.peng@linux.alibaba.com> <2994a6ee-9238-5285-3227-cb7084a834c8@arm.com> <7C1833A8-27A4-4755-9B1E-335C20207A66@linux.alibaba.com> <39d1affb-9cfa-208d-8bf4-f4c802e8c7f9@arm.com> <02BC41EE-6653-4473-91D4-CDEE53D8703D@linux.alibaba.com> From: Valentin Schneider Message-ID: Date: Fri, 16 Aug 2019 18:19:41 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: <02BC41EE-6653-4473-91D4-CDEE53D8703D@linux.alibaba.com> Content-Type: text/plain; charset=gbk Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 16/08/2019 16:39, Liangyan wrote: > Thanks for the feedback. > Add some debug prints and get below log. It seems that pick_next_task_fair throttle the cfs_rq first, then call put_prev_entity to assign runtime to this cfs_rq. > [...] > > Regarding the suggested change, i??m not sure whether it is ok to skip the runtime account for curr task. > Yeah it's probably pretty stupid. IIRC throttled cfs_rq means frozen rq_clock, so any subsequent call to update_curr() on a throttled cfs_rq should lead to an early bailout anyway due to delta_exec <= 0.