From: Eric Dumazet <dada1@cosmosbay.com>
To: linux-kernel@vger.kernel.org
Cc: Andi Kleen <ak@suse.de>
Subject: [POLL] SLAB : Are the 32 and 192 bytes caches really usefull on x86_64 machines ?
Date: Wed, 21 Dec 2005 10:11:51 +0100 [thread overview]
Message-ID: <43A91C57.20102@cosmosbay.com> (raw)
In-Reply-To: <7vbqzadgmt.fsf@assigned-by-dhcp.cox.net>
I wonder if the 32 and 192 bytes caches are worth to be declared in
include/linux/kmalloc_sizes.h, at least on x86_64
(x86_64 : PAGE_SIZE = 4096, L1_CACHE_BYTES = 64)
On my machines, I can say that the 32 and 192 sizes could be avoided in favor
in spending less cpu cycles in __find_general_cachep()
Could some of you post the result of the following command on your machines :
# grep "size-" /proc/slabinfo |grep -v DMA|cut -c1-40
size-131072 0 0 131072
size-65536 0 0 65536
size-32768 2 2 32768
size-16384 0 0 16384
size-8192 13 13 8192
size-4096 161 161 4096
size-2048 40564 42976 2048
size-1024 681 800 1024
size-512 19792 37168 512
size-256 81 105 256
size-192 1218 1280 192
size-64 31278 86907 64
size-128 5457 10380 128
size-32 594 784 32
Thank you
PS : I have no idea why the last lines (size-192, 64, 128, 32) are not ordered...
Eric
next prev parent reply other threads:[~2005-12-21 9:12 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 8:00 [ANNOUNCE] GIT 1.0.0 Junio C Hamano
2005-12-21 9:11 ` Eric Dumazet [this message]
2005-12-21 9:22 ` [POLL] SLAB : Are the 32 and 192 bytes caches really usefull on x86_64 machines ? David S. Miller
2005-12-21 10:03 ` Jan-Benedict Glaw
2005-12-21 9:46 ` Alok kataria
2005-12-21 12:44 ` Ed Tomlinson
2005-12-21 13:20 ` Folkert van Heusden
2005-12-21 13:38 ` Eric Dumazet
2005-12-21 14:09 ` Folkert van Heusden
2005-12-21 16:40 ` Dave Jones
2005-12-21 19:36 ` Folkert van Heusden
2005-12-28 8:32 ` Denis Vlasenko
2005-12-28 8:54 ` Denis Vlasenko
2005-12-28 17:57 ` Andreas Kleen
2005-12-28 21:01 ` Matt Mackall
2005-12-29 1:26 ` Dave Jones
2005-12-30 4:06 ` Steven Rostedt
2006-01-02 8:46 ` Pekka Enberg
2006-01-02 8:51 ` Pekka Enberg
2006-01-02 12:33 ` Steven Rostedt
2006-01-02 12:31 ` Steven Rostedt
2005-12-29 1:29 ` Dave Jones
2005-12-29 1:50 ` Keith Owens
2005-12-29 2:39 ` Dave Jones
2006-01-02 15:03 ` Helge Hafting
2006-01-04 5:26 ` Dave Jones
2005-12-30 21:13 ` Marcelo Tosatti
2005-12-31 20:13 ` Andi Kleen
2005-12-29 19:48 ` Steven Rostedt
2005-12-29 21:16 ` Andi Kleen
2006-01-02 8:37 ` Pekka Enberg
2006-01-02 12:45 ` Andi Kleen
2006-01-02 13:04 ` Pekka J Enberg
2006-01-02 13:56 ` Andi Kleen
2006-01-02 15:09 ` Pekka J Enberg
2006-01-02 15:46 ` Jörn Engel
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=43A91C57.20102@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=ak@suse.de \
--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 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.