mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: "Martin J. Bligh" <mbligh@aracnet.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:29:27 -0800	[thread overview]
Message-ID: <C8C38546F90ABF408A5961FC01FDBF1912E233@fmsmsx405.fm.intel.com> (raw)


Can these (MAX_IO_APICS, MAX_APICS) be moved to sub-arch too, instead of
replacing CONFIG NUMA by CONFIG NUMAQ?

Thanks,
-Venkatesh

> -----Original Message-----
> From: Martin J. Bligh [mailto:mbligh@aracnet.com] 
> Sent: Monday, January 13, 2003 10:30 AM
> To: Protasevich, Natalie
> Cc: Pallipadi, Venkatesh; 'William Lee Irwin III'; Nakajima, 
> Jun; 'Christoph Hellwig'; 'James Cleverdon'; 'Linux Kernel'
> Subject: RE: [PATCH] (0/7) Finish moving NUMA-Q into subarch, cleanup
> 
> 
> > I ran into a couple places where CONFIG_X86_NUMA is still 
> there (replaced
> > now with CONFIG_X86_NUMAQ), which disables following defines:
> 
> Yeah, I saw those the other day. Should probably be replaced with 
> CONFIG_NUMA ... I'll tweak them once I get the last dribbles of Summit
> pushed out to Linus.
> 
> Thanks,
> 
> M.
> 
> 

             reply	other threads:[~2003-01-15 18:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15 18:29 Pallipadi, Venkatesh [this message]
2003-01-15 18:37 ` Martin J. Bligh
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=C8C38546F90ABF408A5961FC01FDBF1912E233@fmsmsx405.fm.intel.com \
    --to=venkatesh.pallipadi@intel.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=mbligh@aracnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®