[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181112041656.GA47272@gmail.com>
Date: Mon, 12 Nov 2018 05:16:56 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Patrick Bellasi <patrick.bellasi@....com>
Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Vincent Guittot <vincent.guittot@...aro.org>,
Quentin Perret <quentin.perret@....com>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Morten Rasmussen <morten.rasmussen@....com>,
Juri Lelli <juri.lelli@...hat.com>,
Todd Kjos <tkjos@...gle.com>,
Steve Muckle <smuckle@...gle.com>,
Suren Baghdasaryan <surenb@...gle.com>
Subject: Re: [PATCH v2 3/3] sched/fair: add lsub_positive and use it
consistently
* Patrick Bellasi <patrick.bellasi@....com> wrote:
> The following pattern:
>
> var -= min_t(typeof(var), var, val);
>
> is used multiple times in fair.c.
>
> The existing sub_positive() already capture that pattern but it adds
> also explicit load-sotre to properly support lockless observations.
> In other cases, the patter above is used to update local, and/or not
> concurrently accessed, variables.
> Let's add a simpler version of sub_positive, targeted to local variables
> updates, which gives the same readability benefits at calling sites
> without enforcing {READ,WRITE}_ONCE barriers.
> +/*
> + * Remove and clamp on negative, from a local variable.
> + *
> + * A variant of sub_positive which do not use explicit load-store
> + * and thus optimized for local variable updates.
I fixed up the two typos ('load-sotre', 'patter'), and fixed eight
grammar mistakes (!) in the changelog and in the code comments, but
*please* read the changelogs and code you are writing, this is scheduler
code after all ...
( Please also use the fn() notation in changelogs consistently in the
future: first you use 'sub_positive()' correctly then it becomes
'sub_positive'. )
Anyway, the fix looks sane so I've applied it to sched/urgent.
Thanks,
Ingo
Powered by blists - more mailing lists