From: Adrian Bunk <bunk@fs.tum.de>
To: "Martin J. Bligh" <mbligh@aracnet.com>, zippel@linux-m68k.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] add required dependencies to X86_NUMAQ
Date: Fri, 25 Jun 2004 01:41:45 +0200 [thread overview]
Message-ID: <20040624234145.GA18303@fs.tum.de> (raw)
In-Reply-To: <3450000.1088120038@flay>
On Thu, Jun 24, 2004 at 04:33:58PM -0700, Martin J. Bligh wrote:
> > If you select another option, you have to ensure that the dependencies
> > of the selected options are met.
> >
> > The following patch adds to X86_NUMAQ the required dependencies for the
> > selected NUMA:
> >
> > --- linux-2.6.7-mm2-full/arch/i386/Kconfig.old 2004-06-24 22:42:32.000000000 +0200
> > +++ linux-2.6.7-mm2-full/arch/i386/Kconfig 2004-06-24 22:44:53.000000000 +0200
> > @@ -65,6 +65,7 @@
> >
> > config X86_NUMAQ
> > bool "NUMAQ (IBM/Sequent)"
> > + depends on SMP && HIGHMEM64G
> > select DISCONTIGMEM
> > select NUMA
> > help
>
> Mmmm. As we already have this:
>
> config NUMA
> bool "Numa Memory Allocation and Scheduler Support"
> depends on SMP && HIGHMEM64G && (X86_NUMAQ || X86_GENERICARCH || (X86_SU
> MMIT && ACPI))
> default n if X86_PC
> default y if (X86_NUMAQ || X86_SUMMIT)
>
> do we really need to cascade it back out like that into everything that
> selects NUMA? Perhaps we should make NUMA select SMP && HIGHMEM64G, rather
> than depend on it?
This would work for SMP, but according to my testing, select doesn't
seem to work with options in choices like HIGHMEM64G.
> M.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2004-06-24 23:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 23:10 [2.6 patch] add required dependencies to X86_NUMAQ Adrian Bunk
2004-06-24 23:33 ` Martin J. Bligh
2004-06-24 23:41 ` Adrian Bunk [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=20040624234145.GA18303@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=zippel@linux-m68k.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.