From: Prashanth Nageshappa <prashanth@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>,
mingo@kernel.org, LKML <linux-kernel@vger.kernel.org>,
roland@kernel.org, Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
efault@gmx.de, Ingo Molnar <mingo@elte.hu>
Subject: [PATCH] sched: reorder lb_env struct members to reduce its size
Date: Tue, 19 Jun 2012 17:47:34 +0530 [thread overview]
Message-ID: <4FE06DDE.7000403@linux.vnet.ibm.com> (raw)
Members of lb_env struct are not in appropriate order to reuse compiler
added padding on 64bit architectures. In this patch we reorder those struct
members and help reduce the size of the structure from 96 bytes to 80
bytes on 64 bit architectures.
Suggested-by: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
Signed-off-by: Prashanth Nageshappa <prashanth@linux.vnet.ibm.com>
---
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 939fd63..96e36fb 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -3102,18 +3102,18 @@ static unsigned long __read_mostly max_load_balance_interval = HZ/10;
struct lb_env {
struct sched_domain *sd;
- int src_cpu;
struct rq *src_rq;
+ int src_cpu;
int dst_cpu;
struct rq *dst_rq;
enum cpu_idle_type idle;
long imbalance;
- unsigned int flags;
struct list_head *tasks;
+ unsigned int flags;
unsigned int loop;
unsigned int loop_break;
unsigned int loop_max;
next reply other threads:[~2012-06-19 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 12:17 Prashanth Nageshappa [this message]
2012-07-06 6:21 ` [tip:sched/core] sched: Reorder 'struct lb_env' members to reduce its size tip-bot for Prashanth Nageshappa
2012-07-24 14:19 ` tip-bot for Prashanth Nageshappa
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=4FE06DDE.7000403@linux.vnet.ibm.com \
--to=prashanth@linux.vnet.ibm.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=roland@kernel.org \
--cc=vatsa@linux.vnet.ibm.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