Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1312203 > unrolled thread

Re: [PATCH 2/4] sched: Consolidate nohz CPU load update code

Started byPeter Zijlstra <peterz@infradead.org>
First post2016-01-19 14:20 +0100
Last post2016-01-19 14:20 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH 2/4] sched: Consolidate nohz CPU load update code Peter Zijlstra <peterz@infradead.org> - 2016-01-19 14:20 +0100

#1312203 — Re: [PATCH 2/4] sched: Consolidate nohz CPU load update code

FromPeter Zijlstra <peterz@infradead.org>
Date2016-01-19 14:20 +0100
SubjectRe: [PATCH 2/4] sched: Consolidate nohz CPU load update code
Message-ID<qSEmu-8o1-13@gated-at.bofh.it>
On Thu, Jan 14, 2016 at 02:18:40PM +0900, Byungchul Park wrote:
> > +	__update_cpu_load_nohz(this_rq, READ_ONCE(jiffies), 0, 0);
> 
> This question is not directly related to this patch but I am just
> curious about... Should we use READ_ONCE on jiffies which is already
> volatile type?

I'd say so, if only because I forever forget that jiffies is declared
volatile and READ_ONCE() makes the intent explicit.

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web