All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yajun Deng <yajun.deng@linux.dev>
To: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
	vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
	rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
	bristot@redhat.com, vschneid@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/3] sched/rt: Move sched_rt_entity::back to CONFIG_RT_GROUP_SCHED
Date: Wed, 8 Nov 2023 19:04:03 +0800	[thread overview]
Message-ID: <cfabc096-105d-438c-8dbc-cfaad5d18a35@linux.dev> (raw)
In-Reply-To: <20231009122244.2394336-1-yajun.deng@linux.dev>


Kindly ping...

Thanks.


On 2023/10/9 20:22, Yajun Deng wrote:
> The member back in struct sched_rt_entity only related to RT_GROUP_SCHED,
> it should not place out of RT_GROUP_SCHED, move back to RT_GROUP_SCHED.
> It will save a few bytes.
>
> The 1st patch is introduce for_each_sched_rt_entity_back() & use it,
> it no functional changes.
>
> The 2nd patch is init 'back' in init_tg_rt_entry, it remove the call to
> back when CONFIG_RT_GROUP_SCHED is disabled.
>
> The 3rd patch is move sched_rt_entity::back to under the
> CONFIG_RT_GROUP_SCHED block, it will save a few bytes.
>
> Yajun Deng (3):
>    sched/rt: Introduce for_each_sched_rt_entity_back() & use it
>    sched/rt: Init 'back' in init_tg_rt_entry
>    sched/headers: Move sched_rt_entity::back to under the
>      CONFIG_RT_GROUP_SCHED block
>
>   include/linux/sched.h |  2 +-
>   kernel/sched/rt.c     | 17 ++++++++++++-----
>   2 files changed, 13 insertions(+), 6 deletions(-)
>

      parent reply	other threads:[~2023-11-08 11:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09 12:22 [PATCH v7 0/3] sched/rt: Move sched_rt_entity::back to CONFIG_RT_GROUP_SCHED Yajun Deng
2023-10-09 12:22 ` [PATCH v7 1/3] sched/rt: Introduce for_each_sched_rt_entity_back() & use it Yajun Deng
2023-10-09 12:22 ` [PATCH v7 2/3] sched/rt: Init 'back' in init_tg_rt_entry Yajun Deng
2023-10-09 12:22 ` [PATCH v7 3/3] sched/headers: Move sched_rt_entity::back to under the CONFIG_RT_GROUP_SCHED block Yajun Deng
2023-11-08 11:04 ` Yajun Deng [this message]

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=cfabc096-105d-438c-8dbc-cfaad5d18a35@linux.dev \
    --to=yajun.deng@linux.dev \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.