[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260113100755.GV830755@noisy.programming.kicks-ass.net>
Date: Tue, 13 Jan 2026 11:07:55 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Wangyang Guo <wangyang.guo@...el.com>
Cc: K Prateek Nayak <kprateek.nayak@....com>,
Ingo Molnar <mingo@...hat.com>, Juri Lelli <juri.lelli@...hat.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Steven Rostedt <rostedt@...dmis.org>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
Valentin Schneider <vschneid@...hat.com>,
linux-kernel@...r.kernel.org,
Shrikanth Hegde <sshegde@...ux.ibm.com>,
Benjamin Lei <benjamin.lei@...el.com>,
Tim Chen <tim.c.chen@...ux.intel.com>,
Tianyou Li <tianyou.li@...el.com>
Subject: Re: [PATCH v2] sched/clock: Avoid false sharing for
sched_clock_irqtime
On Tue, Jan 13, 2026 at 03:48:07PM +0800, Wangyang Guo wrote:
> Read-mostly sched_clock_irqtime may share the same cacheline with
> frequently updated nohz struct. Mark it as __read_mostly to avoid
> false sharing issue.
>
Is there a reason that thing can't be a static_key or so?
Powered by blists - more mailing lists