From: Christoph Lameter <cl@linux.com>
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
linux-mm@kvack.org
Subject: Re: slub: bulk allocation from per cpu partial pages
Date: Thu, 30 Apr 2015 13:40:58 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.11.1504301340150.28784@gentwo.org> (raw)
In-Reply-To: <20150417080610.4ae80965@redhat.com>
On Fri, 17 Apr 2015, Jesper Dangaard Brouer wrote:
> > Ups, I can see that this kernel don't have CONFIG_SLUB_CPU_PARTIAL,
> > I'll re-run tests with this enabled.
>
> Results with CONFIG_SLUB_CPU_PARTIAL.
>
> size -- optimized -- fallback
> bulk 8 -- 16ns -- 22ns
> bulk 16 -- 16ns -- 22ns
> bulk 30 -- 16ns -- 22ns
> bulk 32 -- 16ns -- 22ns
> bulk 64 -- 30ns -- 38ns
That looks better. Can I get the code for testing? Then I can vary the
approach a bit before posting patches? I still want to add a fast path for
allocation from the per node partial list.
--
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-04-30 18:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 18:13 slub bulk alloc: Extract objects from the per cpu slab Christoph Lameter
2015-04-08 22:53 ` Andrew Morton
2015-04-09 14:03 ` Christoph Lameter
2015-04-09 17:16 ` slub: bulk allocation from per cpu partial pages Christoph Lameter
2015-04-16 12:06 ` Jesper Dangaard Brouer
2015-04-16 15:54 ` Christoph Lameter
2015-04-17 5:44 ` Jesper Dangaard Brouer
2015-04-17 6:06 ` Jesper Dangaard Brouer
2015-04-30 18:40 ` Christoph Lameter [this message]
2015-04-30 19:20 ` Jesper Dangaard Brouer
2015-04-09 20:19 ` slub bulk alloc: Extract objects from the per cpu slab Andrew Morton
2015-04-11 2:19 ` Christoph Lameter
2015-04-11 7:25 ` Jesper Dangaard Brouer
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=alpine.DEB.2.11.1504301340150.28784@gentwo.org \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=brouer@redhat.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.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