public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: jamesclv@us.ibm.com, Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] MAX_MP_BUSSES increase
Date: Tue, 08 Jan 2002 01:41:55 -0800	[thread overview]
Message-ID: <15640000.1010482915@flay> (raw)
In-Reply-To: <200201080914.g089EHq21694@butler1.beaverton.ibm.com>
In-Reply-To: <Pine.LNX.4.21.0112261341470.9842-100000@freak.distro.conectiva> <200201080914.g089EHq21694@butler1.beaverton.ibm.com>

> There's a problem with that -- despite its name, CONFIG_MULTIQUAD is used for 
> the old NUMA-Q hardware.  It turns on some memory mapped port I/O code that 
> doesn't have any purpose for other machines.  The PCI bus overflow happens on 
> our new Foster-based boxes that may or may not contain multiple quad CPU 
> boards.
> 
> Still, CONFIG_MULTIQUAD is better than nothing.  It just may take a little 
> bit of redefinition, so long as we can coax the various distros to build 
> their installation and working kernels with CONFIG_MULTIQUAD turned on....

That's not a good idea. You're going to introduce extra switches to every port
IO path, and every IPI (for everybody, not just yourself). CONFIG_MULTIQUAD 
is also used to alter the way that PCI config space writes are done (in later 
patches). I suggest you use a different config option, or construct it dynamically.

Martin.


  reply	other threads:[~2002-01-08 17:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-20  4:28 [PATCH] MAX_MP_BUSSES increase James Cleverdon
2001-12-20  5:55 ` Linus Torvalds
2001-12-20 13:07   ` Ingo Molnar
2001-12-20 17:03     ` Andi Kleen
2001-12-20 22:29       ` James Cleverdon
2001-12-20 22:56         ` Andi Kleen
     [not found]           ` <Pine.LNX.4.33.0112211113570.2196-100000@localhost.localdomain>
2001-12-21  9:14             ` William Lee Irwin III
2001-12-26 15:43 ` Marcelo Tosatti
2002-01-08  9:14   ` James Cleverdon
2002-01-08  9:41     ` Martin J. Bligh [this message]
2002-01-18 21:21       ` James Cleverdon
     [not found] <200112210419.fBL4Jfq08533@butler1.beaverton.ibm.com>
     [not found] ` <Pine.LNX.4.33.0112211131130.2269-100000@localhost.localdomain>
2001-12-21 11:57   ` William Lee Irwin III

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=15640000.1010482915@flay \
    --to=martin.bligh@us.ibm.com \
    --cc=jamesclv@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=torvalds@transmeta.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