mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Andi Kleen <ak@suse.de>
Cc: Pekka J Enberg <penberg@cs.helsinki.fi>,
	Denis Vlasenko <vda@ilport.com.ua>,
	Eric Dumazet <dada1@cosmosbay.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [POLL] SLAB : Are the 32 and 192 bytes caches really usefull on x86_64 machines ?
Date: Mon, 2 Jan 2006 16:46:48 +0100	[thread overview]
Message-ID: <20060102154648.GB673@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <200601021456.23253.ak@suse.de>

On Mon, 2 January 2006 14:56:22 +0100, Andi Kleen wrote:
> 
> I wasn't proposing fully dynamic slabs, just a better default set
> of slabs based on real measurements instead of handwaving (like
> the power of two slabs seemed to have been generated). With separate
> sets for 32bit and 64bit. 
> 
> Also the goal wouldn't be better performance, but just less waste of memory.

My fear would be that this leads to something like the gperf: a
perfect distribution of slab caches - until any tiny detail changes.
But maybe there is a different distribution that is "pretty good" for
all configurations and better than powers of two.

> I suspect such a move could save much more memory on small systems 
> than any of these "make fundamental debugging tools a CONFIG" patches ever.

Unlikely.  SLOB should be better than SLAB for those purposes, no
matter how you arrange the slab caches.

Jörn

-- 
Fancy algorithms are slow when n is small, and n is usually small.
Fancy algorithms have big constants. Until you know that n is
frequently going to be big, don't get fancy.
-- Rob Pike

      parent reply	other threads:[~2006-01-02 15:47 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 ` [POLL] SLAB : Are the 32 and 192 bytes caches really usefull on x86_64 machines ? Eric Dumazet
2005-12-21  9:22   ` 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 [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=20060102154648.GB673@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=ak@suse.de \
    --cc=dada1@cosmosbay.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=vda@ilport.com.ua \
    /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

all inboxes | Powered by JetHome®