From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Christoph Lameter <cl@linux.com>
Cc: iamjoonsoo.kim@lge.com, akpm@linux-foundation.org,
linux-mm@kvack.org, netdev@vger.kernel.org, brouer@redhat.com
Subject: Re: [PATCH mm] slab: implement bulking for SLAB allocator
Date: Tue, 8 Sep 2015 17:54:51 +0200 [thread overview]
Message-ID: <20150908175451.2ce83a0b@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1509081020510.25292@east.gentwo.org>
On Tue, 8 Sep 2015 10:22:32 -0500 (CDT)
Christoph Lameter <cl@linux.com> wrote:
> On Tue, 8 Sep 2015, Jesper Dangaard Brouer wrote:
>
> > Also notice how well bulking maintains the performance when the bulk
> > size increases (which is a soar spot for the slub allocator).
>
> Well you are not actually completing the free action in SLAB. This is
> simply queueing the item to be freed later. Also was this test done on a
> NUMA system? Alien caches at some point come into the picture.
This test was a single CPU benchmark with no congestion or concurrency.
But the code was compiled with CONFIG_NUMA=y.
I don't know the slAb code very well, but the kmem_cache_node->list_lock
looks like a scalability issue. I guess that is what you are referring
to ;-)
--
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-09-08 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 14:21 [PATCH mm] slab: implement bulking for SLAB allocator Jesper Dangaard Brouer
2015-09-08 15:22 ` Christoph Lameter
2015-09-08 15:54 ` Jesper Dangaard Brouer [this message]
2015-09-08 17:10 ` 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=20150908175451.2ce83a0b@redhat.com \
--to=brouer@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.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.