From: Helge Hafting <helgehaf@idb.hist.no>
To: "Udo A. Steinberg" <sorisor@Hell.WH8.TU-Dresden.De>,
linux-kernel@vger.kernel.org
Subject: Re: Request: increase in PCI bus limit
Date: Wed, 31 Jan 2001 10:10:59 +0100 [thread overview]
Message-ID: <3A77D6A3.309A656F@idb.hist.no> (raw)
In-Reply-To: <200101310008.f0V08Wv23250@localhost.localdomain> <3A775FEB.D7614D98@Hell.WH8.TU-Dresden.De>
"Udo A. Steinberg" wrote:
>
> Christopher Neufeld wrote:
>
> > 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.
>
> I guess the cleanest solution would be to allow variable setting of the
> maximum number of PCI busses in the config file, similar to the
> CONFIG_UNIX98_PTY_COUNT setting, so that "exotic" users with 32+ PCI
> busses can boost the standard value according to their needs, without
> having to increase kernel size for the normal users.
>
Wouldn't autodetection be the better solution? Seems to me the kernel
has
no problem detecting all the buses, so why not break the probing into a
two-
pass thing - first pass simply counts buses, second pass allocate memory
and fills in the arrays.
(One-pass is possible too, if dynamic allocation is possible at this
time.)
No config option to worry about, no excess room for 32 buses on ordinary
pc's, no worry for the 100-bus user.
Helge Hafting
-
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/
next prev parent reply other threads:[~2001-01-31 9:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 0:08 Request: increase in PCI bus limit Christopher Neufeld
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
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=3A77D6A3.309A656F@idb.hist.no \
--to=helgehaf@idb.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=sorisor@Hell.WH8.TU-Dresden.De \
/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