From: Michael Ellerman <michael@ellerman.id.au>
To: Li Zhong <zhong@linux.vnet.ibm.com>
Cc: PowerPC email list <linuxppc-dev@lists.ozlabs.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [RFC PATCH powerpc] make CONFIG_NUMA depends on CONFIG_SMP
Date: Fri, 19 Apr 2013 17:20:21 +1000 [thread overview]
Message-ID: <1366356021.5684.3.camel@concordia> (raw)
In-Reply-To: <1366337453.3250.16.camel@ThinkPad-T5421.cn.ibm.com>
On Fri, 2013-04-19 at 10:10 +0800, Li Zhong wrote:
> On Thu, 2013-04-18 at 11:46 +1000, Michael Ellerman wrote:
> > On Wed, May 30, 2012 at 05:31:58PM +0800, Li Zhong wrote:
> > > I'm not sure whether it makes sense to add this dependency to avoid
> > > CONFI_NUMA && !CONFIG_SMP.
> > >
> > > I want to do this because I saw some build errors on next-tree when
> > > compiling with CONFIG_SMP disabled, and it seems they are caused by some
> > > codes under the CONFIG_NUMA #ifdefs.
> >
> > This seems to make sense to me. Can you please repost with a better
> > changelog and a description of the actual build error you were seeing.
>
> I tried it today, but didn't find any build errors any more, guess those
> errors should have already been fixed.
>
> But it seems to me by disabling CONFIG_NUMA when CONFIG_SMP is disabled,
> could at least prevent some unnecessary code being compiled into the
> kernel. (After building a kernel with/without CONFIG_NUMA just now, it
> seems that the vmlinux is ~100K smaller without CONFIG_NUMA).
>
> I'm not sure whether this is still needed.
Yeah we'll leave your patch out. Unless someone cares deeply about the
size of the UP build, I think it's better to just leave them as separate
options.
cheers
prev parent reply other threads:[~2013-04-19 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 9:31 [RFC PATCH powerpc] make CONFIG_NUMA depends on CONFIG_SMP Li Zhong
2013-04-18 1:46 ` Michael Ellerman
2013-04-19 2:10 ` Li Zhong
2013-04-19 7:20 ` Michael Ellerman [this message]
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=1366356021.5684.3.camel@concordia \
--to=michael@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=zhong@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