Linux MM tree latest commits
 help / color / mirror / Atom feed
From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: richard@rsk.demon.co.uk, mingo@elte.hu, peterz@infradead.org,
	rusty@rustcorp.com.au, tj@kernel.org
Subject: + stop_machine-struct-cpu_stopper-remove-alignment-padding-on-64-bits.patch added to -mm tree
Date: Thu, 05 Aug 2010 15:07:05 -0700	[thread overview]
Message-ID: <201008052207.o75M75GM007687@imap1.linux-foundation.org> (raw)


The patch titled
     stop_machine: struct cpu_stopper, remove alignment padding on 64 bits
has been added to the -mm tree.  Its filename is
     stop_machine-struct-cpu_stopper-remove-alignment-padding-on-64-bits.patch

Before you just go and hit "reply", please:
   a) Consider who else should be cc'ed
   b) Prefer to cc a suitable mailing list as well
   c) Ideally: find the original patch on the mailing list and do a
      reply-to-all to that, adding suitable additional cc's

*** Remember to use Documentation/SubmitChecklist when testing your code ***

See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this

The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/

------------------------------------------------------
Subject: stop_machine: struct cpu_stopper, remove alignment padding on 64 bits
From: Richard Kennedy <richard@rsk.demon.co.uk>

Reorder elements in structure cpu_stopper to remove alignment padding on
64 bit builds, this shrinks its size from 40 to 32 bytes saving 8 bytes
per cpu.

Signed-off-by: Richard Kennedy <richard@rsk.demon.co.uk>
Acked-by: Tejun Heo <tj@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Rusty Russell <rusty@rustcorp.com.au>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 kernel/stop_machine.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff -puN kernel/stop_machine.c~stop_machine-struct-cpu_stopper-remove-alignment-padding-on-64-bits kernel/stop_machine.c
--- a/kernel/stop_machine.c~stop_machine-struct-cpu_stopper-remove-alignment-padding-on-64-bits
+++ a/kernel/stop_machine.c
@@ -35,9 +35,9 @@ struct cpu_stop_done {
 /* the actual stopper, one per every possible cpu, enabled on online cpus */
 struct cpu_stopper {
 	spinlock_t		lock;
+	bool			enabled;	/* is this stopper enabled? */
 	struct list_head	works;		/* list of pending works */
 	struct task_struct	*thread;	/* stopper thread */
-	bool			enabled;	/* is this stopper enabled? */
 };
 
 static DEFINE_PER_CPU(struct cpu_stopper, cpu_stopper);
_

Patches currently in -mm which might be from richard@rsk.demon.co.uk are

origin.patch
linux-next.patch
timer_list-remove-alignment-padding-on-64-bit-when-config_timer_stats.patch
buffer_head-remove-redundant-test-from-wait_on_buffer.patch
writeback-reduce-calls-to-global_page_state-in-balance_dirty_pages.patch
stop_machine-struct-cpu_stopper-remove-alignment-padding-on-64-bits.patch


                 reply	other threads:[~2010-08-05 22:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201008052207.o75M75GM007687@imap1.linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mm-commits@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=richard@rsk.demon.co.uk \
    --cc=rusty@rustcorp.com.au \
    --cc=tj@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