From: Magnus Damm <magnus@valinux.co.jp>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH for review] [140/145] i386: mark cpu_dev structures as __cpuinitdata
Date: Mon, 14 Aug 2006 10:26:23 +0900 [thread overview]
Message-ID: <1155518783.5764.10.camel@localhost> (raw)
In-Reply-To: <200608111126_MC3-1-C7CA-65CE@compuserve.com>
On Fri, 2006-08-11 at 11:24 -0400, Chuck Ebbert wrote:
> In-Reply-To: <20060810193740.9133413C0B@wotan.suse.de>
>
> On Thu, 10 Aug 2006 21:37:40 +0200, Andi Kleen wrote:
>
> > From: Magnus Damm <magnus@valinux.co.jp>
> >
> > The different cpu_dev structures are all used from __cpuinit callers what
> > I can tell. So mark them as __cpuinitdata instead of __initdata. I am a
> > little bit unsure about arch/i386/common.c:default_cpu, especially when it
> > comes to the purpose of this_cpu.
>
> But none of these CPUs supports hotplug and only one (AMD) does SMP.
> So this is just wasting space in the kernel at runtime.
How could this be wasting space? If you compile with CONFIG_HOTPLUG_CPU
disabled then __cpuinitdata will become __initdata - ie the same as
before. Not a single byte wasted what I can tell.
The first version of this patch simply added a missing __init to some
function, but I was then corrected by akpm that __cpuinit should be used
instead.
Thanks,
/ magnus
next prev parent reply other threads:[~2006-08-14 1:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 15:24 [PATCH for review] [140/145] i386: mark cpu_dev structures as __cpuinitdata Chuck Ebbert
2006-08-11 16:07 ` Andi Kleen
2006-08-14 1:26 ` Magnus Damm [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-15 6:46 Chuck Ebbert
2006-08-15 7:43 ` Arjan van de Ven
2006-08-15 16:59 ` Dave Jones
[not found] <20060810 935.775038000@suse.de>
2006-08-10 19:37 ` Andi Kleen
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=1155518783.5764.10.camel@localhost \
--to=magnus@valinux.co.jp \
--cc=76306.1226@compuserve.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.