From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Christoph Lameter <cl@linux.com>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Alexander Duyck <alexander.duyck@gmail.com>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
brouer@redhat.com
Subject: Re: [PATCH 3/3] slub: build detached freelist with look-ahead
Date: Thu, 23 Jul 2015 13:09:17 +0200 [thread overview]
Message-ID: <20150723130917.6e46e7d0@redhat.com> (raw)
In-Reply-To: <20150723063423.GG4449@js1304-P5Q-DELUXE>
On Thu, 23 Jul 2015 15:34:24 +0900 Joonsoo Kim <iamjoonsoo.kim@lge.com> wrote:
> On Wed, Jul 22, 2015 at 01:28:19AM +0200, Jesper Dangaard Brouer wrote:
> > On Tue, 21 Jul 2015 08:50:36 -0500 (CDT)
> > Christoph Lameter <cl@linux.com> wrote:
> >
> > > On Mon, 20 Jul 2015, Jesper Dangaard Brouer wrote:
> > >
> > > > Yes, I think it is merged... how do I turn off merging?
> > >
> > > linux/Documentation/kernel-parameters.txt
> > >
> > > slab_nomerge [MM]
> > > Disable merging of slabs with similar size. May be
> > > necessary if there is some reason to distinguish
> > > allocs to different slabs. Debug options disable
> > > merging on their own.
> > > For more information see Documentation/vm/slub.txt.
> >
> > I was hoping I could define this per slub runtime. Any chance this
> > would be made possible?
>
> It's not possible to set/reset slab merge in runtime. Once merging
> happens, one slab could have objects from different kmem_caches so we
> can't separate it cleanly. Current best approach is to prevent merging
> when creating new kmem_cache by introducing new slab flag
> like as SLAB_NO_MERGE.
Yes, the best option would be a new flag (e.g. SLAB_NO_MERGE) when
creating the kmem_cache.
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Sr. Network Kernel Developer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
--
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:[~2015-07-23 11:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 16:01 [PATCH 0/3] slub: introducing detached freelist Jesper Dangaard Brouer
2015-07-15 16:01 ` [PATCH 1/3] slub: extend slowpath __slab_free() to handle bulk free Jesper Dangaard Brouer
2015-07-15 16:54 ` Christoph Lameter
2015-07-15 16:02 ` [PATCH 2/3] slub: optimize bulk slowpath free by detached freelist Jesper Dangaard Brouer
2015-07-15 16:56 ` Christoph Lameter
2015-07-15 16:02 ` [PATCH 3/3] slub: build detached freelist with look-ahead Jesper Dangaard Brouer
2015-07-16 9:57 ` Jesper Dangaard Brouer
2015-07-20 2:54 ` Joonsoo Kim
2015-07-20 21:28 ` Jesper Dangaard Brouer
2015-07-21 13:50 ` Christoph Lameter
2015-07-21 23:28 ` Jesper Dangaard Brouer
2015-07-23 6:34 ` Joonsoo Kim
2015-07-23 11:09 ` Jesper Dangaard Brouer [this message]
2015-07-23 14:14 ` Christoph Lameter
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=20150723130917.6e46e7d0@redhat.com \
--to=brouer@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.duyck@gmail.com \
--cc=cl@linux.com \
--cc=hannes@stressinduktion.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).