Searched hist:"590 d6979" (Results 1 – 6 of 6) sorted by relevance
/openbmc/linux/kernel/sched/ |
H A D | stop_task.c | 590d6979 Thu Dec 19 15:44:52 CST 2019 Steven Rostedt (VMware) <rostedt@goodmis.org> sched: Force the address order of each sched class descriptor
In order to make a micro optimization in pick_next_task(), the order of the sched class descriptor address must be in the same order as their priority to each other. That is:
&idle_sched_class < &fair_sched_class < &rt_sched_class < &dl_sched_class < &stop_sched_class
In order to guarantee this order of the sched class descriptors, add each one into their own data section and force the order in the linker script.
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://lore.kernel.org/r/157675913272.349305.8936736338884044103.stgit@localhost.localdomain 590d6979 Thu Dec 19 15:44:52 CST 2019 Steven Rostedt (VMware) <rostedt@goodmis.org> sched: Force the address order of each sched class descriptor In order to make a micro optimization in pick_next_task(), the order of the sched class descriptor address must be in the same order as their priority to each other. That is: &idle_sched_class < &fair_sched_class < &rt_sched_class < &dl_sched_class < &stop_sched_class In order to guarantee this order of the sched class descriptors, add each one into their own data section and force the order in the linker script. Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://lore.kernel.org/r/157675913272.349305.8936736338884044103.stgit@localhost.localdomain
|
H A D | idle.c | 590d6979 Thu Dec 19 15:44:52 CST 2019 Steven Rostedt (VMware) <rostedt@goodmis.org> sched: Force the address order of each sched class descriptor
In order to make a micro optimization in pick_next_task(), the order of the sched class descriptor address must be in the same order as their priority to each other. That is:
&idle_sched_class < &fair_sched_class < &rt_sched_class < &dl_sched_class < &stop_sched_class
In order to guarantee this order of the sched class descriptors, add each one into their own data section and force the order in the linker script.
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://lore.kernel.org/r/157675913272.349305.8936736338884044103.stgit@localhost.localdomain 590d6979 Thu Dec 19 15:44:52 CST 2019 Steven Rostedt (VMware) <rostedt@goodmis.org> sched: Force the address order of each sched class descriptor In order to make a micro optimization in pick_next_task(), the order of the sched class descriptor address must be in the same order as their priority to each other. That is: &idle_sched_class < &fair_sched_class < &rt_sched_class < &dl_sched_class < &stop_sched_class In order to guarantee this order of the sched class descriptors, add each one into their own data section and force the order in the linker script. Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://lore.kernel.org/r/157675913272.349305.8936736338884044103.stgit@localhost.localdomain
|
H A D | rt.c | 590d6979 Thu Dec 19 15:44:52 CST 2019 Steven Rostedt (VMware) <rostedt@goodmis.org> sched: Force the address order of each sched class descriptor
In order to make a micro optimization in pick_next_task(), the order of the sched class descriptor address must be in the same order as their priority to each other. That is:
&idle_sched_class < &fair_sched_class < &rt_sched_class < &dl_sched_class < &stop_sched_class
In order to guarantee this order of the sched class descriptors, add each one into their own data section and force the order in the linker script.
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://lore.kernel.org/r/157675913272.349305.8936736338884044103.stgit@localhost.localdomain 590d6979 Thu Dec 19 15:44:52 CST 2019 Steven Rostedt (VMware) <rostedt@goodmis.org> sched: Force the address order of each sched class descriptor In order to make a micro optimization in pick_next_task(), the order of the sched class descriptor address must be in the same order as their priority to each other. That is: &idle_sched_class < &fair_sched_class < &rt_sched_class < &dl_sched_class < &stop_sched_class In order to guarantee this order of the sched class descriptors, add each one into their own data section and force the order in the linker script. Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://lore.kernel.org/r/157675913272.349305.8936736338884044103.stgit@localhost.localdomain
|
H A D | deadline.c | 590d6979 Thu Dec 19 15:44:52 CST 2019 Steven Rostedt (VMware) <rostedt@goodmis.org> sched: Force the address order of each sched class descriptor
In order to make a micro optimization in pick_next_task(), the order of the sched class descriptor address must be in the same order as their priority to each other. That is:
&idle_sched_class < &fair_sched_class < &rt_sched_class < &dl_sched_class < &stop_sched_class
In order to guarantee this order of the sched class descriptors, add each one into their own data section and force the order in the linker script.
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://lore.kernel.org/r/157675913272.349305.8936736338884044103.stgit@localhost.localdomain 590d6979 Thu Dec 19 15:44:52 CST 2019 Steven Rostedt (VMware) <rostedt@goodmis.org> sched: Force the address order of each sched class descriptor In order to make a micro optimization in pick_next_task(), the order of the sched class descriptor address must be in the same order as their priority to each other. That is: &idle_sched_class < &fair_sched_class < &rt_sched_class < &dl_sched_class < &stop_sched_class In order to guarantee this order of the sched class descriptors, add each one into their own data section and force the order in the linker script. Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://lore.kernel.org/r/157675913272.349305.8936736338884044103.stgit@localhost.localdomain
|
H A D | fair.c | 590d6979 Thu Dec 19 15:44:52 CST 2019 Steven Rostedt (VMware) <rostedt@goodmis.org> sched: Force the address order of each sched class descriptor
In order to make a micro optimization in pick_next_task(), the order of the sched class descriptor address must be in the same order as their priority to each other. That is:
&idle_sched_class < &fair_sched_class < &rt_sched_class < &dl_sched_class < &stop_sched_class
In order to guarantee this order of the sched class descriptors, add each one into their own data section and force the order in the linker script.
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://lore.kernel.org/r/157675913272.349305.8936736338884044103.stgit@localhost.localdomain 590d6979 Thu Dec 19 15:44:52 CST 2019 Steven Rostedt (VMware) <rostedt@goodmis.org> sched: Force the address order of each sched class descriptor In order to make a micro optimization in pick_next_task(), the order of the sched class descriptor address must be in the same order as their priority to each other. That is: &idle_sched_class < &fair_sched_class < &rt_sched_class < &dl_sched_class < &stop_sched_class In order to guarantee this order of the sched class descriptors, add each one into their own data section and force the order in the linker script. Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://lore.kernel.org/r/157675913272.349305.8936736338884044103.stgit@localhost.localdomain
|
/openbmc/linux/include/asm-generic/ |
H A D | vmlinux.lds.h | 590d6979 Thu Dec 19 15:44:52 CST 2019 Steven Rostedt (VMware) <rostedt@goodmis.org> sched: Force the address order of each sched class descriptor
In order to make a micro optimization in pick_next_task(), the order of the sched class descriptor address must be in the same order as their priority to each other. That is:
&idle_sched_class < &fair_sched_class < &rt_sched_class < &dl_sched_class < &stop_sched_class
In order to guarantee this order of the sched class descriptors, add each one into their own data section and force the order in the linker script.
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://lore.kernel.org/r/157675913272.349305.8936736338884044103.stgit@localhost.localdomain 590d6979 Thu Dec 19 15:44:52 CST 2019 Steven Rostedt (VMware) <rostedt@goodmis.org> sched: Force the address order of each sched class descriptor In order to make a micro optimization in pick_next_task(), the order of the sched class descriptor address must be in the same order as their priority to each other. That is: &idle_sched_class < &fair_sched_class < &rt_sched_class < &dl_sched_class < &stop_sched_class In order to guarantee this order of the sched class descriptors, add each one into their own data section and force the order in the linker script. Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://lore.kernel.org/r/157675913272.349305.8936736338884044103.stgit@localhost.localdomain
|