From: Andrew Morton <akpm@osdl.org>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: andrea@suse.de, agruen@suse.de, linux-kernel@vger.kernel.org
Subject: Re: slab-alignment-rework.patch in -mc
Date: Tue, 20 Apr 2004 00:24:23 -0700 [thread overview]
Message-ID: <20040420002423.469cca01.akpm@osdl.org> (raw)
In-Reply-To: <4084017C.5080706@colorfullife.com>
Manfred Spraul <manfred@colorfullife.com> wrote:
>
> > No best-guess must
> >be made automatically by the slab code, rounding it to 16 bytes.
> >
> If you pass 0 as align to kmem_cache_create, then it's rounded to L2
> size. It's questionable if that's really the best thing - on
> uniprocessor, 16-byte might result is better performance - there is no
> risk of false sharing.
Just about every time we've cared to investigate slab alignment, we've
ended up removing SLAB_HWCACHE_ALIGN. It seems inappropriate that _any_ of
the inode caches have this set, for example.
And this patch appears to have taken the effective size of the buffer_head
from 48 bytes up to 64, which hurts.
So I do think that we should either make "align=0" translate to "pack them
densely" or do the big sweep across all kmem_cache_create() callsites.
If the latter, while we're there, let's remove SLAB_HWCACHE_ALIGN where it
isn't obviously appropriate. I'd imagine that being able to fit more inodes
into memory is a net win over the occasional sharing effect, for example.
next prev parent reply other threads:[~2004-04-20 7:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1082383751.6746.33.camel@f235.suse.de>
2004-04-19 16:25 ` Andrea Arcangeli
2004-04-19 16:42 ` Manfred Spraul
2004-04-20 0:26 ` Andrea Arcangeli
2004-04-20 7:24 ` Andrew Morton [this message]
2004-04-20 14:49 ` Andrea Arcangeli
2004-04-20 17:23 ` Manfred Spraul
2004-04-20 18:25 ` Andrew Morton
2004-04-20 18:52 ` Linus Torvalds
2004-04-21 17:22 ` Manfred Spraul
2004-04-21 21:46 ` Andrew Morton
2004-04-20 18:53 ` Arjan van de Ven
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=20040420002423.469cca01.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=agruen@suse.de \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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
all inboxes | Powered by JetHome®