[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3193fcc9-c672-19d9-a2e2-ad67809dd20b@infradead.org>
Date: Wed, 8 Jun 2022 08:33:40 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Steven Lung <1030steven@...il.com>, mingo@...hat.com
Cc: peterz@...radead.org, juri.lelli@...hat.com,
vincent.guittot@...aro.org, dietmar.eggemann@....com,
rostedt@...dmis.org, bsegall@...gle.com, mgorman@...e.de,
bristot@...hat.com, vschneid@...hat.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sched/pelt: Fix bracket typo
On 6/8/22 08:00, Steven Lung wrote:
> The second bracket describing the range is inverted, this patch
> will fix it.
>
> Signed-off-by: Steven Lung <1030steven@...il.com>
> ---
> kernel/sched/pelt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/sched/pelt.c b/kernel/sched/pelt.c
> index 0f3107682..ed82cfba9 100644
> --- a/kernel/sched/pelt.c
> +++ b/kernel/sched/pelt.c
> @@ -233,7 +233,7 @@ ___update_load_sum(u64 now, struct sched_avg *sa,
> * When syncing *_avg with *_sum, we must take into account the current
> * position in the PELT segment otherwise the remaining part of the segment
> * will be considered as idle time whereas it's not yet elapsed and this will
> - * generate unwanted oscillation in the range [1002..1024[.
Is the above the same as range [1002..1024).
? I.e. 1002-1023 inclusive (or 1024 excluded)?
> + * generate unwanted oscillation in the range [1002..1024].
> *
> * The max value of *_sum varies with the position in the time segment and is
> * equals to :
--
~Randy
Powered by blists - more mailing lists