From: Alex Williamson <alex.williamson@hp.com>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: "Brown, Len" <len.brown@intel.com>,
linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: RE: [ACPI] ACPI owner_id limit too low
Date: Thu, 08 Dec 2005 15:21:10 -0700 [thread overview]
Message-ID: <1134080471.2476.9.camel@tdi> (raw)
In-Reply-To: <971FCB6690CD0E4898387DBF7552B90E03A96856@orsmsx403.amr.corp.intel.com>
On Thu, 2005-12-08 at 14:03 -0800, Moore, Robert wrote:
> We have increased the number of owner IDs to 255 in the most recent
> version of ACPICA, 20051202. This should hit Linux soon.
>
> Additionally, we plan to conserve OwnerIDs by not using them for tables
> that can never be unloaded, to be implemented in a future release.
> However, 255 Ids should be plenty for now.
>
> Here is the text from the release memo:
>
> Increased the number of available Owner Ids for namespace object
> tracking from 32 to 255. This should eliminate the OWNER_ID_LIMIT
> exceptions seen on some machines with a large number of ACPI tables
> (either static or dynamic).
Hi Bob,
Sorry if I wasn't clear, I'm worried about what happens in the
interim. The problem will be fixed in ACPICA 20051202, but we have at
least one, likely two stable kernels that will be tagged before that
ACPICA version hits the upstream kernel. We can hit the owner_id limit
fairly easily on a few development systems. How many stable kernels do
we want out in the wild with such a low owner_id limit? Bumping it up
to 64, while not ideal, is sufficient for our current usage, and I think
the patch is trivial enough that it could be included quickly. Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
prev parent reply other threads:[~2005-12-08 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 22:03 [ACPI] ACPI owner_id limit too low Moore, Robert
2005-12-08 22:21 ` Alex Williamson [this message]
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=1134080471.2476.9.camel@tdi \
--to=alex.williamson@hp.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.moore@intel.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