From: Hyeonggon Yoo <42.hyeyoo@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [RFC] Some questions and an idea on SLUB/SLAB
Date: Sat, 9 Oct 2021 00:40:58 +0000 [thread overview]
Message-ID: <20211009004058.GA4992@kvm.asia-northeast3-a.c.our-ratio-313919.internal> (raw)
In-Reply-To: <YWDjZ+KlkV2wKShh@casper.infradead.org>
On Sat, Oct 09, 2021 at 01:33:43AM +0100, Matthew Wilcox wrote:
> On Sat, Oct 09, 2021 at 12:19:03AM +0000, Hyeonggon Yoo wrote:
> > - Is there a reason that SLUB does not implement cache coloring?
> > it will help utilizing hardware cache. Especially in block layer,
> > they are literally *squeezing* its performance now.
>
> Have you tried turning off cache colouring in SLAB and seeing if
> performance changes? My impression is that it's useful for caches
> with low associativity (direct mapped / 2-way / 4-way), but loses
> its effectiveness for caches with higher associativity. For example,
> my laptop:
>
> L1 Data Cache: 48KB, 12-way associative, 64 byte line size
> L1 Instruction Cache: 32KB, 8-way associative, 64 byte line size
> L2 Unified Cache: 1280KB, 20-way associative, 64 byte line size
> L3 Unified Cache: 12288KB, 12-way associative, 64 byte line size
>
> I very much doubt that cache colouring is still useful for this machine.
Hello Matthew,
What benchmark did you use for test?
-
Hyeonggon
next prev parent reply other threads:[~2021-10-09 0:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 0:19 [RFC] Some questions and an idea on SLUB/SLAB Hyeonggon Yoo
2021-10-09 0:33 ` Matthew Wilcox
2021-10-09 0:40 ` Hyeonggon Yoo [this message]
2021-10-09 2:02 ` Hyeonggon Yoo
2021-10-09 11:45 ` Almost no difference Hyeonggon Yoo
2021-10-11 7:13 ` [RFC] Some questions and an idea on SLUB/SLAB Christoph Lameter
2021-10-13 3:44 ` Hyeonggon Yoo
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=20211009004058.GA4992@kvm.asia-northeast3-a.c.our-ratio-313919.internal \
--to=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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.