From: Kees Cook <keescook@chromium.org>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>
Cc: x86@kernel.org, Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] sched: task_struct: Fill unconditional hole induced by sched_entity
Date: Tue, 5 Oct 2021 21:48:51 -0700 [thread overview]
Message-ID: <202110052146.D639C70@keescook> (raw)
In-Reply-To: <20210924025450.4138503-1-keescook@chromium.org>
On Thu, Sep 23, 2021 at 07:54:50PM -0700, Kees Cook wrote:
> With struct sched_entity before the other sched entities, its alignment
> won't induce a struct hole. This saves 64 bytes in defconfig task_struct:
Friendly ping. Can someone snag this for -tip please?
Thanks!
-Kees
>
> Before:
> ...
> unsigned int rt_priority; /* 120 4 */
>
> /* XXX 4 bytes hole, try to pack */
>
> /* --- cacheline 2 boundary (128 bytes) --- */
> const struct sched_class * sched_class; /* 128 8 */
>
> /* XXX 56 bytes hole, try to pack */
>
> /* --- cacheline 3 boundary (192 bytes) --- */
> struct sched_entity se __attribute__((__aligned__(64))); /* 192 448 */
> /* --- cacheline 10 boundary (640 bytes) --- */
> struct sched_rt_entity rt; /* 640 48 */
> struct sched_dl_entity dl __attribute__((__aligned__(8))); /* 688 224 */
> /* --- cacheline 14 boundary (896 bytes) was 16 bytes ago --- */
>
> After:
> ...
> unsigned int rt_priority; /* 120 4 */
>
> /* XXX 4 bytes hole, try to pack */
>
> /* --- cacheline 2 boundary (128 bytes) --- */
> struct sched_entity se __attribute__((__aligned__(64))); /* 128 448 */
> /* --- cacheline 9 boundary (576 bytes) --- */
> struct sched_rt_entity rt; /* 576 48 */
> struct sched_dl_entity dl __attribute__((__aligned__(8))); /* 624 224 */
> /* --- cacheline 13 boundary (832 bytes) was 16 bytes ago --- */
>
> Summary diff:
> - /* size: 7040, cachelines: 110, members: 188 */
> + /* size: 6976, cachelines: 109, members: 188 */
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> include/linux/sched.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index 39039ce8ac4c..27ed1d40028f 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -775,10 +775,10 @@ struct task_struct {
> int normal_prio;
> unsigned int rt_priority;
>
> - const struct sched_class *sched_class;
> struct sched_entity se;
> struct sched_rt_entity rt;
> struct sched_dl_entity dl;
> + const struct sched_class *sched_class;
>
> #ifdef CONFIG_SCHED_CORE
> struct rb_node core_node;
> --
> 2.30.2
>
--
Kees Cook
next prev parent reply other threads:[~2021-10-06 4:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 2:54 [PATCH] sched: task_struct: Fill unconditional hole induced by sched_entity Kees Cook
2021-10-06 4:48 ` Kees Cook [this message]
2021-10-06 9:27 ` Peter Zijlstra
2021-10-06 16:31 ` Kees Cook
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=202110052146.D639C70@keescook \
--to=keescook@chromium.org \
--cc=bp@alien8.de \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).