From: Len Brown <len.brown@intel.com>
To: linux-acpi@vger.kernel.org
Subject: ACPI slab stats
Date: Wed, 8 Mar 2006 04:09:40 -0500 [thread overview]
Message-ID: <200603080409.41213.len.brown@intel.com> (raw)
FYI, ACPI slab usage on Viro's box.
1344 * 96 bytes = 129KB, which is significant.
[02:40] <viro> acpi_operand: ffffffff801d90af <acpi_os_acquire_object+b/3e> 1344
[02:40] <viro> size-2048: ffffffff802180fc <acpi_thermal_add+6b/223> 1
[02:40] <viro> size-1024: ffffffff80213331 <acpi_processor_add+65/10a> 1
[02:41] <viro> size-1024: ffffffff8021a01e <acpi_add_single_object+7b/22e> 56
[02:41] <viro> size-512: ffffffff801ff0f8 <acpi_ut_callocate+57/d3> 4
[02:41] <viro> size-192: ffffffff801ff0f8 <acpi_ut_callocate+57/d3> 5
[02:41] <viro> size-32: ffffffff801d8a0c <acpi_os_create_lock+31/c9> 1
[02:41] <viro> size-32: ffffffff801d96ad <acpi_evaluate_integer+8e/2b0> 6
[02:41] <viro> size-32: ffffffff80208071 <acpi_button_add+6b/3a3> 2
[02:41] <viro> size-32: ffffffff8020a85a <acpi_fan_add+74/18f> 1
[02:41] <viro> size-32: ffffffff80210968 <acpi_pci_bind+f1/480> 4
[02:42] <viro> size-32: ffffffff80211008 <acpi_pci_bind_root+f6/246> 1
[02:42] <viro> size-128: ffffffff801ff0f8 <acpi_ut_callocate+57/d3> 801
[02:42] <viro> size-64: ffffffff801d8b4d <acpi_os_create_semaphore+32/124> 15
[02:42] <viro> size-64: ffffffff801ff0f8 <acpi_ut_callocate+57/d3> 13
[02:42] <viro> size-64: ffffffff801ff18a <acpi_ut_create_list+16/40> 2
[02:42] <viro> size-64: ffffffff8020dcf7 <acpi_pci_root_add+80/429> 1
[02:42] <viro> size-64: ffffffff8020f2ae <acpi_pci_link_add+72/26d> 12
[02:43] <viro> size-64: ffffffff8020f8c0 <acpi_pci_irq_add_entry+75/1ae> 40
[02:43] <viro> size-64: ffffffff8021a0f3 <acpi_add_single_object+150/22e> 1
next reply other threads:[~2006-03-08 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 9:09 Len Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-09 6:00 ACPI slab stats Brown, Len
2006-03-09 21:30 Moore, Robert
2006-03-10 15:50 Moore, Robert
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=200603080409.41213.len.brown@intel.com \
--to=len.brown@intel.com \
--cc=linux-acpi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.