mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christopher Neufeld <neufeld@linuxcare.com>
To: linux-kernel@vger.kernel.org
Subject: Request: increase in PCI bus limit
Date: Tue, 30 Jan 2001 16:08:32 -0800	[thread overview]
Message-ID: <200101310008.f0V08Wv23250@localhost.localdomain> (raw)

   Hello,

   I'm working at a customer site with custom hardware.  The 2.4.0 series
kernel almost works out of the box, but the machine has 52 PCI busses.
Plans are to produce a 4-way box which would have over 80 PCI busses.  The
file include/asm-i386/mpspec.h allocates space for 32 busses in the
definition of the macro MAX_MP_BUSSES.  When 52 busses are probed, some
arrays are filled out past their ends (there is no bounds checking
performed on the array filling), and the kernel oopses out.  The only patch
which has to be applied to make Linux run stably on these systems is to
increase that limit.  Would it be possible to bump it up to 128, or even
256, in later 2.4.* kernel releases?  That would allow this customer to
work with an unpatched kernel, at the cost of an additional 3.5 kB of
variables in the kernel.

   Thank you for any help.
   For completeness, here's the patch (against 2.4.0):

--- linux-2.4.0/include/asm-i386/mpspec.h.orig  Tue Jan 30 16:06:08 2001
+++ linux-2.4.0/include/asm-i386/mpspec.h       Tue Jan 30 16:06:21 2001
@@ -157,7 +157,7 @@
  */
 
 #define MAX_IRQ_SOURCES 128
-#define MAX_MP_BUSSES 32
+#define MAX_MP_BUSSES 256
 enum mp_bustype {
        MP_BUS_ISA = 1,
        MP_BUS_EISA,



-- 
 Christopher Neufeld		 		 neufeld@linuxcare.com
 Home page:  http://caliban.physics.utoronto.ca/neufeld/Intro.html
 "Don't edit reality for the sake of simplicity"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2001-01-31  0:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-31  0:08 Christopher Neufeld [this message]
2001-01-31  0:36 ` Timur Tabi
2001-01-31  1:44   ` List User
2001-01-31  9:15   ` James Sutherland
2001-01-31  0:44 ` Udo A. Steinberg
2001-01-31  9:10   ` Helge Hafting
2001-01-31  1:31 Bernd Eckenfels
2001-01-31  1:32 Bernd Eckenfels
2001-01-31  6:55 ` Peter Samuelson
2001-01-31 20:38   ` George
2001-01-31 20:45     ` Scott Laird
2001-01-31 20:52       ` nick
2001-01-31 20:58       ` Dan Hollis
2001-02-10  0:29       ` Dr. Kelsey Hudson
2001-02-24 13:46     ` Ralf Baechle
2001-01-31 10:27 Manfred Spraul
2001-01-31 16:26 Christopher Neufeld

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=200101310008.f0V08Wv23250@localhost.localdomain \
    --to=neufeld@linuxcare.com \
    --cc=linux-kernel@vger.kernel.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 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®