public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Richard Kennedy <richard@rsk.demon.co.uk>
Cc: Tejun Heo <tj@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] stop_machine: struct cpu_stopper, remove alignment padding on 64 bits
Date: Thu, 05 Aug 2010 13:40:35 +0200	[thread overview]
Message-ID: <1281008435.1923.1820.camel@laptop> (raw)
In-Reply-To: <1281006717.2000.12.camel@castor.rsk>

On Thu, 2010-08-05 at 12:11 +0100, Richard Kennedy wrote:
> 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>

Looks good to me. Tejun will you take it or should I send it Ingo wards?

> ---
> diff --git a/kernel/stop_machine.c b/kernel/stop_machine.c
> index 70f8d90..4372ccb 100644
> --- a/kernel/stop_machine.c
> +++ b/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);
> 
> 



  parent reply	other threads:[~2010-08-05 11:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-05 11:11 [PATCH] stop_machine: struct cpu_stopper, remove alignment padding on 64 bits Richard Kennedy
2010-08-05 11:39 ` Tejun Heo
2010-08-05 11:40 ` Peter Zijlstra [this message]
2010-08-05 11:44   ` Tejun Heo

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=1281008435.1923.1820.camel@laptop \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=richard@rsk.demon.co.uk \
    --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