From: Pekka J Enberg <penberg@cs.Helsinki.FI>
To: Christoph Lameter <clameter@sgi.com>
Cc: Manfred Spraul <manfred@colorfullife.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [patch 2/2] slab: always consider arch mandated alignment
Date: Thu, 27 Jul 2006 08:47:16 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0607270844440.28990@sbz-30.cs.Helsinki.FI> (raw)
In-Reply-To: <Pine.LNX.4.58.0607270823140.28805@sbz-30.cs.Helsinki.FI>
On Thu, 27 Jul 2006, Pekka J Enberg wrote:
> Yes and that's what we have been saying all along. When you want
> performance, you use SLAB_HWCACHE_ALIGN and let the allocator do its job.
> I don't see much point from API point of view for the caller to explicitly
> ask for a given alignment and then in addition pass a 'yes I really meant'
> flag (SLAB_DEBUG_OVERRIDE).
Btw, /proc/slabinfo for UML with defconfig reveals change for only one
cache with my patch applied. The 'dquot' cache is created by dquot_init in
fs/dquot.c and doesn't really seem to need the alignment for anything...
Pekka
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-07-27 5:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060722110601.GA9572@osiris.boeblingen.de.ibm.com>
[not found] ` <Pine.LNX.4.64.0607220748160.13737@schroedinger.engr.sgi.com>
[not found] ` <20060722162607.GA10550@osiris.ibm.com>
[not found] ` <Pine.LNX.4.64.0607221241130.14513@schroedinger.engr.sgi.com>
[not found] ` <20060723073500.GA10556@osiris.ibm.com>
[not found] ` <Pine.LNX.4.64.0607230558560.15651@schroedinger.engr.sgi.com>
[not found] ` <20060723162427.GA10553@osiris.ibm.com>
2006-07-26 8:50 ` [patch 1/2] slab: always consider caller " Heiko Carstens, Heiko Carstens
2006-07-26 8:51 ` [patch 2/2] slab: always consider arch " Heiko Carstens, Heiko Carstens
2006-07-26 10:05 ` Pekka J Enberg
2006-07-26 10:13 ` Heiko Carstens
2006-07-26 10:37 ` Pekka J Enberg
2006-07-26 10:52 ` Heiko Carstens
2006-07-26 11:16 ` Pekka J Enberg
2006-07-26 11:26 ` Heiko Carstens
2006-07-26 18:06 ` Manfred Spraul
2006-07-26 18:19 ` Christoph Lameter
2006-07-26 18:45 ` Manfred Spraul
2006-07-26 18:59 ` Christoph Lameter
2006-07-26 19:28 ` Manfred Spraul
2006-07-26 19:31 ` Christoph Lameter
2006-07-26 19:37 ` Manfred Spraul
2006-07-26 19:47 ` Christoph Lameter
2006-07-27 5:33 ` Pekka J Enberg
2006-07-27 5:47 ` Pekka J Enberg [this message]
2006-07-27 4:24 ` Pekka J Enberg
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=Pine.LNX.4.58.0607270844440.28990@sbz-30.cs.Helsinki.FI \
--to=penberg@cs.helsinki.fi \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.com \
--cc=schwidefsky@de.ibm.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