From: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
To: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Jesse Barnes <jbarnes-sJ/iWh9BUns@public.gmane.org>,
"Grover,
Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Bjorn Helgaas <bjorn_helgaas-VXdhtT5mjnY@public.gmane.org>,
"Moore,
Robert" <robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: #define ACPI_MAX_TABLES 256
Date: Mon, 6 Oct 2003 15:34:33 -0600 [thread overview]
Message-ID: <200310061534.33430.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE0CC8753-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
On Friday 03 October 2003 11:56 am, Brown, Len wrote:
> Anybody know where the value 256 came from?
> (looks like we used to define ACPI_MAX_TABLES as ACPI_TABLE_COUNT about
> a year ago)
>
> We use ACPI_MAX_TABLES to limit how many RSDT or XSDT entries we look
> at, but I didn't see any limit in the spec, so I was wondering if this
> came from some practical experience.
256 was just picked out of the blue. It was previously about 17,
and we overflowed that with an HP box that was about half the
size of the current largest box. So the minimum to support a
fully configured box would have been around 35.
Bjorn
g
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-10-06 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 17:56 #define ACPI_MAX_TABLES 256 Brown, Len
[not found] ` <BF1FE1855350A0479097B3A0D2A80EE0CC8753-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2003-10-06 21:34 ` Bjorn Helgaas [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-06 2:37 Brown, Len
[not found] ` <F7DC2337C7631D4386A2DF6E8FB22B300229FE09-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-12-06 16:01 ` Jesse Barnes
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=200310061534.33430.bjorn.helgaas@hp.com \
--to=bjorn.helgaas-vxdhtt5mjny@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=bjorn_helgaas-VXdhtT5mjnY@public.gmane.org \
--cc=jbarnes-sJ/iWh9BUns@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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