From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org
Subject: Re: Support concurrent local and remote frees and allocs on a slab.
Date: Sun, 6 May 2007 12:24:47 -0700 [thread overview]
Message-ID: <20070506122447.0d5b83e1.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705052243490.29846@schroedinger.engr.sgi.com>
On Sat, 5 May 2007 22:45:26 -0700 (PDT) Christoph Lameter <clameter@sgi.com> wrote:
> On Sat, 5 May 2007, Christoph Lameter wrote:
>
> > Hmmmm... I can take this even further and get another 20% if I take the
> > critical components of slab_alloc and slab_free and inline them into
> > kfree, kmem_cache_alloc and friends. I went from 5.8MB without this
> > patch to now 8 MB/sec with this patch and the rather ugly inlining.
>
> Hmmm... Nope. That was the effect of screwing up kfree so that no memory
> is ever freed. Interesting that this increases performance...
Yes, is is interesting, considering all our lovingly-crafted efforts to
keep that sort of memory hot in the CPU cache.
Or was it netperf-to-localhost?
--
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:[~2007-05-06 19:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 3:28 Christoph Lameter
2007-05-06 4:59 ` Christoph Lameter
2007-05-06 5:45 ` Christoph Lameter
2007-05-06 19:24 ` Andrew Morton [this message]
2007-05-07 15:15 ` Christoph Lameter
2007-05-07 18:39 ` Christoph Lameter
2007-05-07 18:54 ` Andrew Morton
2007-05-07 18:58 ` Christoph Lameter
2007-05-07 20:32 ` Andrew Morton
2007-05-07 21:50 ` Andrew Morton
2007-05-07 21:55 ` Christoph Lameter
2007-05-08 0:56 ` Christoph Lameter
2007-05-08 22:05 ` 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=20070506122447.0d5b83e1.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=clameter@sgi.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