From: "Martin J. Bligh" <mbligh@aracnet.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
"Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
Christoph Hellwig <hch@infradead.org>,
James Cleverdon <jamesclv@us.ibm.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] (0/7) Finish moving NUMA-Q into subarch, cleanup
Date: Wed, 15 Jan 2003 10:37:30 -0800 [thread overview]
Message-ID: <949530000.1042655849@titus> (raw)
In-Reply-To: <C8C38546F90ABF408A5961FC01FDBF1912E233@fmsmsx405.fm.intel.com>
> Can these (MAX_IO_APICS, MAX_APICS) be moved to sub-arch too, instead of
Not easily, at least not without creating a circular dependency problem.
Try it ;-)
I guess we chould create another subarch header file just for these if we
really have to, but that seem like overkill.
If you can come up with a clean patch (check it compiles on uniproc with
and without IO/APIC turned on, and standard SMP as well), I'd really
be interested to see it ... would be most helpful
> replacing CONFIG NUMA by CONFIG NUMAQ?
Actually replacing CONFIG_X86_NUMA with CONFIG_NUMA ... and we could
do (CONFIG_NUMA || CONFIG_BIGSMP) instead. But you're right, subarch
would be much better if you can find a way.
M.
next prev parent reply other threads:[~2003-01-15 18:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 18:29 [PATCH] (0/7) Finish moving NUMA-Q into subarch, cleanup Pallipadi, Venkatesh
2003-01-15 18:37 ` Martin J. Bligh [this message]
2003-01-15 19:05 ` William Lee Irwin III
-- strict thread matches above, loose matches on Subject: below --
2003-01-15 19:30 Protasevich, Natalie
2003-01-15 20:17 ` William Lee Irwin III
2003-01-15 18:41 Protasevich, Natalie
2003-01-13 18:19 Protasevich, Natalie
2003-01-13 18:30 ` Martin J. Bligh
2003-01-07 20:44 Martin J. Bligh
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=949530000.1042655849@titus \
--to=mbligh@aracnet.com \
--cc=Natalie.Protasevich@UNISYS.com \
--cc=hch@infradead.org \
--cc=jamesclv@us.ibm.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.com \
--cc=wli@holomorphy.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 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.