The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Kirill Tkhai <ktkhai@virtuozzo.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	mingo@redhat.com, juri.lelli@redhat.com,
	vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
	bsegall@google.com, mgorman@suse.de,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] sched: Micro optimization in pick_next_task() and in check_preempt_curr()
Date: Thu, 19 Dec 2019 17:46:37 +0300	[thread overview]
Message-ID: <11d755e9-e4f8-dd9e-30b0-45aebe260b2f@virtuozzo.com> (raw)
In-Reply-To: <20191219094330.0e44c748@gandalf.local.home>

On 19.12.2019 17:43, Steven Rostedt wrote:
> On Thu, 19 Dec 2019 17:25:40 +0300
> Kirill Tkhai <ktkhai@virtuozzo.com> wrote:
> 
>> (17:19:25) nbjoerg: but it is not guarenteed behavior
>> (17:19:50) nbjoerg: if for some strange reason you really need to enforce relative orders of global objects, put them in consecutively named sections
> 
> Which appears to work. I tried this patch on top of yours:
> 
> Not sure how this does with locality though.

Hm, I'm not sure, but AFAIR some (all?) sections are aligned at 4K.
Will this bring holes (4K-sizeof(struct sched_class)) in address
space?


> -- Steve
> 
> diff --git a/include/asm-generic/vmlinux.lds.h b/include/asm-generic/vmlinux.lds.h
> index e00f41aa8ec4..ff12a422ff19 100644
> --- a/include/asm-generic/vmlinux.lds.h
> +++ b/include/asm-generic/vmlinux.lds.h
> @@ -108,6 +108,13 @@
>  #define SBSS_MAIN .sbss
>  #endif
>  
> +#define SCHED_DATA				\
> +	*(__idle_sched_class)			\
> +	*(__fair_sched_class)			\
> +	*(__rt_sched_class)			\
> +	*(__dl_sched_class)			\
> +	*(__stop_sched_class)
> +
>  /*
>   * Align to a 32 byte boundary equal to the
>   * alignment gcc 4.5 uses for a struct
> @@ -308,6 +315,7 @@
>  #define DATA_DATA							\
>  	*(.xiptext)							\
>  	*(DATA_MAIN)							\
> +	SCHED_DATA							\
>  	*(.ref.data)							\
>  	*(.data..shared_aligned) /* percpu related */			\
>  	MEM_KEEP(init.data*)						\
> diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
> index 43323f875cb9..5abdbe569f93 100644
> --- a/kernel/sched/deadline.c
> +++ b/kernel/sched/deadline.c
> @@ -2428,7 +2428,8 @@ static void prio_changed_dl(struct rq *rq, struct task_struct *p,
>  	}
>  }
>  
> -const struct sched_class dl_sched_class = {
> +const struct sched_class dl_sched_class
> +	__attribute__((section("__dl_sched_class"))) = {
>  	.next			= &rt_sched_class,
>  	.enqueue_task		= enqueue_task_dl,
>  	.dequeue_task		= dequeue_task_dl,
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 08a233e97a01..e745fe0e0cd3 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -10745,7 +10745,8 @@ static unsigned int get_rr_interval_fair(struct rq *rq, struct task_struct *task
>  /*
>   * All the scheduling class methods:
>   */
> -const struct sched_class fair_sched_class = {
> +const struct sched_class fair_sched_class
> +	__attribute__((section("__fair_sched_class"))) = {
>  	.next			= &idle_sched_class,
>  	.enqueue_task		= enqueue_task_fair,
>  	.dequeue_task		= dequeue_task_fair,
> diff --git a/kernel/sched/idle.c b/kernel/sched/idle.c
> index ffa959e91227..700a9c826f0e 100644
> --- a/kernel/sched/idle.c
> +++ b/kernel/sched/idle.c
> @@ -454,7 +454,8 @@ static void update_curr_idle(struct rq *rq)
>  /*
>   * Simple, special scheduling class for the per-CPU idle tasks:
>   */
> -const struct sched_class idle_sched_class = {
> +const struct sched_class idle_sched_class
> +	__attribute__((section("__idle_sched_class"))) = {
>  	/* .next is NULL */
>  	/* no enqueue/yield_task for idle tasks */
>  
> diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
> index e591d40fd645..5d3f9bcddaeb 100644
> --- a/kernel/sched/rt.c
> +++ b/kernel/sched/rt.c
> @@ -2354,7 +2354,8 @@ static unsigned int get_rr_interval_rt(struct rq *rq, struct task_struct *task)
>  		return 0;
>  }
>  
> -const struct sched_class rt_sched_class = {
> +const struct sched_class rt_sched_class
> +	__attribute__((section("__rt_sched_class"))) = {
>  	.next			= &fair_sched_class,
>  	.enqueue_task		= enqueue_task_rt,
>  	.dequeue_task		= dequeue_task_rt,
> diff --git a/kernel/sched/stop_task.c b/kernel/sched/stop_task.c
> index 4c9e9975684f..03bc7530ff75 100644
> --- a/kernel/sched/stop_task.c
> +++ b/kernel/sched/stop_task.c
> @@ -115,7 +115,8 @@ static void update_curr_stop(struct rq *rq)
>  /*
>   * Simple, special scheduling class for the per-CPU stop tasks:
>   */
> -const struct sched_class stop_sched_class = {
> +const struct sched_class stop_sched_class
> +	__attribute__((section("__stop_sched_class"))) = {
>  	.next			= &dl_sched_class,
>  
>  	.enqueue_task		= enqueue_task_stop,
> 


  reply	other threads:[~2019-12-19 14:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19 12:39 [PATCH RFC] sched: Micro optimization in pick_next_task() and in check_preempt_curr() Kirill Tkhai
2019-12-19 13:12 ` Peter Zijlstra
2019-12-19 14:02   ` Peter Zijlstra
2019-12-19 14:25     ` Kirill Tkhai
2019-12-19 14:31       ` Kirill Tkhai
2019-12-19 14:43       ` Steven Rostedt
2019-12-19 14:46         ` Kirill Tkhai [this message]
2019-12-19 14:59           ` Steven Rostedt
2019-12-19 15:20             ` [PATCH v2] " Kirill Tkhai
2019-12-19 15:40               ` Steven Rostedt
2019-12-19 16:08                 ` Kirill Tkhai
2019-12-19 16:22                   ` Steven Rostedt
2019-12-19 20:16                     ` Kirill Tkhai
2019-12-19 20:20                       ` Steven Rostedt
2019-12-19 16:05               ` Steven Rostedt
2019-12-19 14:04   ` [Q] ld: Does LTO reorder ro variables in two files? Kirill Tkhai
2019-12-19 15:21     ` Jeff Law
2019-12-19 15:30       ` Kirill Tkhai
2019-12-19 15:45     ` Alexander Monakov
2019-12-19 16:08       ` Kirill Tkhai
2019-12-19 13:50 ` [PATCH RFC] sched: Micro optimization in pick_next_task() and in check_preempt_curr() Steven Rostedt
2019-12-19 13:53   ` Kirill Tkhai
2019-12-19 13:53   ` Peter Zijlstra
2020-06-25 11:53 ` [tip: sched/core] sched: Force the address order of each sched class descriptor tip-bot2 for Steven Rostedt (VMware)

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=11d755e9-e4f8-dd9e-30b0-45aebe260b2f@virtuozzo.com \
    --to=ktkhai@virtuozzo.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 \
    /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