Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp3371665pxb; Mon, 17 Jan 2022 18:54:10 -0800 (PST) X-Google-Smtp-Source: ABdhPJwoYym/Q4kiBIpvSMAHd2EaS30S2YLivCEtEC1KPdKYlBRhDzNj+iJSPjnVrPH4i0LCCSw8 X-Received: by 2002:a63:8f08:: with SMTP id n8mr21515719pgd.161.1642474450132; Mon, 17 Jan 2022 18:54:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642474450; cv=none; d=google.com; s=arc-20160816; b=vsW4RPBqov4cG8bEKyuPpJid9ImSbcHFshZWl5Xqk3Or/P3gf2Mbc5PDpF97YWW57h 0N6pk9yF6o1fEqMj46bFLBzopAtbdK0kT4UJYKEOKwHpBhhcaJ357c4AXH4Vzx+YnPgo 3Iw4yW33rGg98dw2F9if6y+vCiMGtXXY4p3s9kFDKykhkhVBH7cdLI3nd6kKVvwfbLSB NfM+x5NA7YP/GGosK+Ju9orK7t+R96hxORepWSi4qPuxSD2iATbRsSqlqaV0PdCLCoUH h8c0z8uW83xcnpabCDf3HC9uU9k7zcIVSJDkCrTdITIY2hh9hsakJKLta/W9D/QEUjg+ oq2g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=QKizg9vb1bMC/Rpg8PcXzKz/r6Jw7RAb5GldlqzIDCw=; b=nPXPsXjnf+q64ys3QSZqnKaA8aRylyfpl9soFvn03hjIWNccHs9YXJ4ccBjjZz2+Im bm8uL+p7O3QkOAEwTy6YXR1WHjTofzI1qk33PLLnjBw9QDzXJPly01YYIDZxyZlnMrTf Ja+Iv8uOuohgVbHyinDVKAb0xw9ml3WU+HImvFrbsAMMM+a/gY36uEomfu3+SiJrOW6/ AN7klAmcYyscqbb26d2DvcWMb0GBynFT5Z7y6+uDFqyaEliNm5yDMfPBvynhAEL1GEyl NXXnlgwOnTH16mbKYPGRYMXbmWvnUqs7ZWJYXkMCTypUWBASCUlsYoKOMmv6yGlqXAUu gd4Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=kCOUQDHA; 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=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g5si10478783pfv.285.2022.01.17.18.53.55; Mon, 17 Jan 2022 18:54:10 -0800 (PST) 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=@linaro.org header.s=google header.b=kCOUQDHA; 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=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238020AbiAQRbn (ORCPT + 99 others); Mon, 17 Jan 2022 12:31:43 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52766 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239334AbiAQRbi (ORCPT ); Mon, 17 Jan 2022 12:31:38 -0500 Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5BE9CC06173F for ; Mon, 17 Jan 2022 09:31:38 -0800 (PST) Received: by mail-lf1-x12a.google.com with SMTP id m3so46328508lfu.0 for ; Mon, 17 Jan 2022 09:31:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=QKizg9vb1bMC/Rpg8PcXzKz/r6Jw7RAb5GldlqzIDCw=; b=kCOUQDHA2SRlcCSdViUg2MvHcKix52LweJCzvRNwwvpYs+sURZ5u+2Ma7tB/CZ2q2K el4CNFDWY1n5/YyvAwoADNuMWgwBldq+9Wsf77OT8VVDuen3hj2J8rWeZG/NPkLHKSKZ d60WP9ezAp7F6+v7do7bkLQdAFoJCoZxCLoPi845RUDK2ADA2Yyk7rgNLVXLFzFImFnX WWQyWWxqsI5POGk0dBh03MPb8rwxBj3VD8LxyLKwo/9p5nhc1oYrtyMR7wuuQUHxq78C b0uw9GQChDk7/Jxu8h1HsmrSV1kp/N9wy0Pid3WKlh8mkxmjd3Ul2Zl8h3QQBnEi7pNV kvEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QKizg9vb1bMC/Rpg8PcXzKz/r6Jw7RAb5GldlqzIDCw=; b=5f3oMD1Fh88fQcUKEhSLL/mk/TkLxrJGPlqD7yP7TV9OmluTQ8LZw9EmOqlb5mxXcF KXIP9767n1/RrCXU+/oK8zPUyllfGsvrJ7UAeyb+X4Fi9FA3Cbnmdb04nSrr0cpBaGU7 sYDR5a0IqMDBtPQN2Hvb7u2bLbydkmkxb7inADXi3HG5Jm2fNQ2+bDGiLR+HSQ1/aGxb fvl46J2y7w4UIMR+1IRJrlNjDfKon5v0SKM+dJjH12CYcF7cNFcDtOq3oHM4awzsl7Io 39oVw+HIQq/ywQoa4FmpxRJtqyynt7vXz4uqTOGbUAjARMO3JHVUWQZpMW3gHWzU1/CR 0hVg== X-Gm-Message-State: AOAM530t1qWKvnklF0Jw33EH/rffUaC1EPcOPW45RlQtREl6nFmfOARV E4RrrObK47S7C+1cGwS9H/+Klj4yQRuizObjX5+s6Q== X-Received: by 2002:a19:f811:: with SMTP id a17mr16941381lff.18.1642440696541; Mon, 17 Jan 2022 09:31:36 -0800 (PST) MIME-Version: 1.0 References: <20220112161230.836326-1-vincent.donnefort@arm.com> <20220112161230.836326-3-vincent.donnefort@arm.com> In-Reply-To: <20220112161230.836326-3-vincent.donnefort@arm.com> From: Vincent Guittot Date: Mon, 17 Jan 2022 18:31:25 +0100 Message-ID: Subject: Re: [PATCH v2 2/7] sched/fair: Decay task PELT values during migration To: Vincent Donnefort Cc: peterz@infradead.org, mingo@redhat.com, linux-kernel@vger.kernel.org, dietmar.eggemann@arm.com, Valentin.Schneider@arm.com, Morten.Rasmussen@arm.com, Chris.Redpath@arm.com, qperret@google.com, Lukasz.Luba@arm.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 12 Jan 2022 at 17:14, Vincent Donnefort wrote: > > Before being migrated to a new CPU, a task sees its PELT values > synchronized with rq last_update_time. Once done, that same task will also > have its sched_avg last_update_time reset. This means the time between > the migration and the last clock update (B) will not be accounted for in > util_avg and a discontinuity will appear. This issue is amplified by the > PELT clock scaling. If the clock hasn't been updated while the CPU is > idle, clock_pelt will not be aligned with clock_task and that time (A) > will be also lost. > > ---------|----- A -----|-----------|------- B -----|> > clock_pelt clock_task clock now > > This is especially problematic for asymmetric CPU capacity systems which > need stable util_avg signals for task placement and energy estimation. > > Ideally, this problem would be solved by updating the runqueue clocks > before the migration. But that would require taking the runqueue lock > which is quite expensive [1]. Instead estimate the missing time and update > the task util_avg with that value: > > A + B = clock_task - clock_pelt + sched_clock_cpu() - clock > > Neither clock_task, clock_pelt nor clock can be accessed without the > runqueue lock. The new runqueue clock_pelt_lag is therefore created and > encode those three values. > > clock_pelt_lag = clock - clock_task + clock_pelt > > And we can then write the missing time as follow: > > A + B = sched_clock_cpu() - clock_pelt_lag > > The B. part of the missing time is however an estimation that doesn't take > into account IRQ and Paravirt time. > > Now we have an estimation for A + B, we can create an estimator for the > PELT value at the time of the migration. We need for this purpose to > inject last_update_time which is a combination of both clock_pelt and > lost_idle_time. The latter is a time value which is completely lost form a > PELT point of view and must be ignored. And finally, we can write: > > rq_clock_pelt_estimator() = last_update_time + A + B > = last_update_time + > sched_clock_cpu() - clock_pelt_lag > > [1] https://lore.kernel.org/all/20190709115759.10451-1-chris.redpath@arm.com/ > > Signed-off-by: Vincent Donnefort > > diff --git a/kernel/sched/core.c b/kernel/sched/core.c > index 06cf7620839a..11c6aeef4583 100644 > --- a/kernel/sched/core.c > +++ b/kernel/sched/core.c > @@ -618,6 +618,12 @@ struct rq *task_rq_lock(struct task_struct *p, struct rq_flags *rf) > } > } > > +static void update_rq_clock_pelt_lag(struct rq *rq) > +{ > + u64_u32_store(rq->clock_pelt_lag, > + rq->clock - rq->clock_task + rq->clock_pelt); This has several shortfalls: - have a look at cfs_rq_clock_pelt() and rq_clock_pelt(). What you name clock_pelt in your commit message and is used to update PELT and saved in se->avg.last_update_time is : rq->clock_pelt - rq->lost_idle_time - cfs_rq->throttled_clock_task_time - you are doing this whatever the state of the cpu : idle or not. But the clock cycles are not accounted for in the same way in both cases. - (B) doesn't seem to be accurate as you skip irq and steal time accounting and you don't apply any scale invariance if the cpu is not idle - IIUC your explanation in the commit message above, the (A) period seems to be a problem only when idle but you apply it unconditionally. If cpu is idle you can assume that clock_pelt should be equal to clock_task but you can't if cpu is not idle otherwise your sync will be inaccurate and defeat the primary goal of this patch. If your problem with clock_pelt is that the pending idle time is not accounted for when entering idle but only at the next update (update blocked load or wakeup of a thread). This patch below should fix this and remove your A. diff --git a/kernel/sched/pelt.h b/kernel/sched/pelt.h index e06071bf3472..855877be4dd8 100644 --- a/kernel/sched/pelt.h +++ b/kernel/sched/pelt.h @@ -114,6 +114,7 @@ static inline void update_idle_rq_clock_pelt(struct rq *rq) { u32 divider = ((LOAD_AVG_MAX - 1024) << SCHED_CAPACITY_SHIFT) - LOAD_AVG_MAX; u32 util_sum = rq->cfs.avg.util_sum; + u64 now = rq_clock_task(rq); util_sum += rq->avg_rt.util_sum; util_sum += rq->avg_dl.util_sum; @@ -127,7 +128,10 @@ static inline void update_idle_rq_clock_pelt(struct rq *rq) * rq's clock_task. */ if (util_sum >= divider) - rq->lost_idle_time += rq_clock_task(rq) - rq->clock_pelt; + rq->lost_idle_time += now - rq->clock_pelt; + + /* The rq is idle, we can sync to clock_task */ + rq->clock_pelt = now; } static inline u64 rq_clock_pelt(struct rq *rq) --- > +} > + > /* > * RQ-clock updating methods: > */ > @@ -674,6 +680,7 @@ static void update_rq_clock_task(struct rq *rq, s64 delta) > update_irq_load_avg(rq, irq_delta + steal); > #endif > update_rq_clock_pelt(rq, delta); > + update_rq_clock_pelt_lag(rq); > } > > void update_rq_clock(struct rq *rq) > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c > index 99ea9540ece4..046d5397eb8a 100644 > --- a/kernel/sched/fair.c > +++ b/kernel/sched/fair.c > @@ -6852,6 +6852,14 @@ select_task_rq_fair(struct task_struct *p, int prev_cpu, int wake_flags) > > static void detach_entity_cfs_rq(struct sched_entity *se); > > +static u64 rq_clock_pelt_estimator(struct rq *rq, u64 last_update_time) > +{ > + u64 pelt_lag = sched_clock_cpu(cpu_of(rq)) - > + u64_u32_load(rq->clock_pelt_lag); Have you evaluated the impact of calling sched_clock_cpu(cpu_of(rq)) for a remote cpu ? especially with a huge number of migration and concurrent access from several cpus > + > + return last_update_time + pelt_lag; > +} > + > /* > * Called immediately before a task is migrated to a new CPU; task_cpu(p) and > * cfs_rq_of(p) references at time of call are still valid and identify the > @@ -6859,6 +6867,9 @@ static void detach_entity_cfs_rq(struct sched_entity *se); > */ > static void migrate_task_rq_fair(struct task_struct *p, int new_cpu) > { > + struct sched_entity *se = &p->se; > + struct rq *rq = task_rq(p); > + > /* > * As blocked tasks retain absolute vruntime the migration needs to > * deal with this by subtracting the old and adding the new > @@ -6866,7 +6877,6 @@ static void migrate_task_rq_fair(struct task_struct *p, int new_cpu) > * the task on the new runqueue. > */ > if (READ_ONCE(p->__state) == TASK_WAKING) { > - struct sched_entity *se = &p->se; > struct cfs_rq *cfs_rq = cfs_rq_of(se); > > se->vruntime -= u64_u32_load(cfs_rq->min_vruntime); > @@ -6877,26 +6887,32 @@ static void migrate_task_rq_fair(struct task_struct *p, int new_cpu) > * In case of TASK_ON_RQ_MIGRATING we in fact hold the 'old' > * rq->lock and can modify state directly. > */ > - lockdep_assert_rq_held(task_rq(p)); > - detach_entity_cfs_rq(&p->se); > + lockdep_assert_rq_held(rq); > + detach_entity_cfs_rq(se); > > } else { > + u64 now; > + > + remove_entity_load_avg(se); > + > /* > - * We are supposed to update the task to "current" time, then > - * its up to date and ready to go to new CPU/cfs_rq. But we > - * have difficulty in getting what current time is, so simply > - * throw away the out-of-date time. This will result in the > - * wakee task is less decayed, but giving the wakee more load > - * sounds not bad. > + * Here, the task's PELT values have been updated according to > + * the current rq's clock. But if that clock hasn't been > + * updated in a while, a substantial idle time will be missed, > + * leading to an inflation after wake-up on the new rq. > + * > + * Estimate the PELT clock lag, and update sched_avg to ensure > + * PELT continuity after migration. > */ > - remove_entity_load_avg(&p->se); > + now = rq_clock_pelt_estimator(rq, se->avg.last_update_time); > + __update_load_avg_blocked_se(now, se); > } > > /* Tell new CPU we are migrated */ > - p->se.avg.last_update_time = 0; > + se->avg.last_update_time = 0; > > /* We have migrated, no longer consider this task hot */ > - p->se.exec_start = 0; > + se->exec_start = 0; > > update_scan_period(p, new_cpu); > } > diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h > index f1a445efdc63..fdf2a9e54c0e 100644 > --- a/kernel/sched/sched.h > +++ b/kernel/sched/sched.h > @@ -1027,8 +1027,13 @@ struct rq { > /* Ensure that all clocks are in the same cache line */ > u64 clock_task ____cacheline_aligned; > u64 clock_pelt; > + u64 clock_pelt_lag; > unsigned long lost_idle_time; > > +#ifndef CONFIG_64BIT > + u64 clock_pelt_lag_copy; > +#endif > + > atomic_t nr_iowait; > > #ifdef CONFIG_SCHED_DEBUG > -- > 2.25.1 >