From: Vincent Donnefort <vincent.donnefort@arm.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: mingo@redhat.com, peterz@infradead.org,
vincent.guittot@linaro.org, linux-kernel@vger.kernel.org,
dietmar.eggemann@arm.com, lukasz.luba@arm.com,
valentin.schneider@arm.com
Subject: Re: [PATCH] sched/fair: provide u64 read for 32-bits arch helper
Date: Mon, 27 Jul 2020 13:05:21 +0100 [thread overview]
Message-ID: <20200727120520.GA257620@e120877-lin.cambridge.arm.com> (raw)
In-Reply-To: <20200727112454.GB55660@gmail.com>
Hi,
On Mon, Jul 27, 2020 at 01:24:54PM +0200, Ingo Molnar wrote:
>
> * vincent.donnefort@arm.com <vincent.donnefort@arm.com> wrote:
>
> > From: Vincent Donnefort <vincent.donnefort@arm.com>
> >
> > Introducing two macro helpers u64_32read() and u64_32read_set_copy() to
> > factorize the u64 vminruntime and last_update_time read on a 32-bits
> > architecture. Those new helpers encapsulate smp_rmb() and smp_wmb()
> > synchronization and therefore, have a small penalty in set_task_rq_fair()
> > and init_cfs_rq().
> >
> > The choice of using a macro over an inline function is driven by the
> > conditional u64 variable copy declarations.
>
> Could you please explain how "conditional u64 variable copy
> declarations" prevents us to use an inline function for this
I meant, as the "copy" variable [vminruntime|last_update_time]_copy, is
declared only in the !CONFIG_64BIT case, a function call would fail when
CONFIG_64BIT is set.
u64_32read(cfs_rq->min_vruntime, cfs_rq->min_vruntime_copy);
^
not declared
I could rephrase this part to something more understandable ?
>
> > +/*
> > + * u64_32read() / u64_32read_set_copy()
> > + *
> > + * Use the copied u64 value to protect against data race. This is only
> > + * applicable for 32-bits architectures.
> > + */
> > +#if !defined(CONFIG_64BIT) && defined(CONFIG_SMP)
> > +# define u64_32read(val, copy) \
> > +({ \
> > + u64 _val; \
> > + u64 _val_copy; \
> > + \
> > + do { \
> > + _val_copy = copy; \
> > + /* \
> > + * paired with u64_32read_set_copy, ordering access \
> > + * to val and copy. \
> > + */ \
> > + smp_rmb(); \
> > + _val = val; \
> > + } while (_val != _val_copy); \
> > + \
> > + _val; \
> > +})
> > +# define u64_32read_set_copy(val, copy) \
> > +do { \
> > + /* paired with u64_32read, ordering access to val and copy */ \
> > + smp_wmb(); \
> > + copy = val; \
> > +} while (0)
> > +#else
> > +# define u64_32read(val, copy) (val)
> > +# define u64_32read_set_copy(val, copy) do { } while (0)
> > +#endif
> > +
>
> Thanks,
>
> Ingo
--
Vincent
next prev parent reply other threads:[~2020-07-27 12:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 10:59 vincent.donnefort
2020-07-27 11:24 ` Ingo Molnar
2020-07-27 12:05 ` Vincent Donnefort [this message]
2020-07-27 12:38 ` peterz
2020-07-27 15:23 ` Vincent Donnefort
2020-07-28 11:13 ` peterz
2020-07-28 12:00 ` peterz
2020-07-28 19:53 ` Vincent Donnefort
2020-08-18 18:11 ` Vincent Donnefort
2020-07-28 9:09 ` Lukasz Luba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200727120520.GA257620@e120877-lin.cambridge.arm.com \
--to=vincent.donnefort@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®