From: Peter Zijlstra <peterz@infradead.org>
To: Josh Don <joshdon@google.com>
Cc: Blake Jones <blakejones@google.com>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Madadi Vineeth Reddy <vineethr@linux.ibm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] sched: reorder some fields in struct rq
Date: Fri, 5 Dec 2025 11:49:41 +0100 [thread overview]
Message-ID: <20251205104941.GR2528459@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <CABk29NskTSV1JUT=_08sQXaWkpHyHb5RKYLVeTSHdx+QMiw5dA@mail.gmail.com>
On Thu, Dec 04, 2025 at 02:56:47PM -0800, Josh Don wrote:
> Hi Blake,
>
> On Mon, Dec 1, 2025 at 6:37 PM Blake Jones <blakejones@google.com> wrote:
> >
> > This colocates some hot fields in "struct rq" to be on the same cache line
> > as others that are often accessed at the same time or in similar ways.
> [snip]
> > Signed-off-by: Blake Jones <blakejones@google.com>
> > Reviewed-by: Madadi Vineeth Reddy <vineethr@linux.ibm.com>
> > Tested-by: Madadi Vineeth Reddy <vineethr@linux.ibm.com>
>
> Sorry, I thought I had already included a review tag when I responded
> to the earlier version of this.
>
> Reviewed-by: Josh Don <joshdon@google.com>
>
> > ---
> > kernel/sched/sched.h | 80 +++++++++++++++++++++++++++-----------------
> > 1 file changed, 50 insertions(+), 30 deletions(-)
> >
> > v4 -> v5 changes:
> > - Resynced with sched/core.
> > Link to v4: https://lore.kernel.org/lkml/20251029185458.3040228-1-blakejones@google.com/T/#u
> >
> > v3 -> v4 changes:
> > - Updated based on review comments from peterz@infradead.org:
> > updated block comment in struct rq, moved "nr_iowait" to the end of the
> > structure, and added "__no_randomize_layout" tag to the structure.
> > Link to v3: https://lore.kernel.org/lkml/20251028080348.2177469-1-blakejones@google.com/T/#u
> >
> > v2 -> v3 changes:
> > - Resynced and retested. Results are consistent with v2.
> > Link to v2: https://lore.kernel.org/lkml/20250730205644.2595052-1-blakejones@google.com/T/#u
> >
> > v1 -> v2 changes:
> > - Resynced to tip/sched/core tree, which has removed CONFIG_SMP.
> > Link to v1: https://lore.kernel.org/lkml/20250722201339.1198239-1-blakejones@google.com/T/#u
> >
> > v1 was sent on July 22 of this year, over four months ago.
>
> The patch is straightforward and the results look compelling;
> Peter/Ingo, any thoughts?
I've stuck it on the pile for post -rc1 time.
next prev parent reply other threads:[~2025-12-05 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 2:37 Blake Jones
2025-12-04 22:56 ` Josh Don
2025-12-05 10:49 ` Peter Zijlstra [this message]
2025-12-06 1:41 ` Blake Jones
2026-01-12 8:03 ` [tip: sched/core] sched: Reorder " tip-bot2 for Blake Jones
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=20251205104941.GR2528459@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=blakejones@google.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=joshdon@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
--cc=vincent.guittot@linaro.org \
--cc=vineethr@linux.ibm.com \
--cc=vschneid@redhat.com \
/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®