From: Pekka Enberg <penberg@kernel.org>
To: Christoph Lameter <cl@linux.com>
Cc: David Rientjes <rientjes@google.com>, linux-mm@kvack.org
Subject: Re: slub: free slabs without holding locks (V2)
Date: Sun, 31 Jul 2011 19:19:32 +0300 [thread overview]
Message-ID: <CAOJsxLF_BaPGx9CcYewKHs0FQdK_HfNXW5ptu2w9nAs47+GodQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1107141033031.30512@router.home>
On Thu, Jul 14, 2011 at 6:35 PM, Christoph Lameter <cl@linux.com> wrote:
> There are two situations in which slub holds a lock while releasing
> pages:
>
> A. During kmem_cache_shrink()
> B. During kmem_cache_close()
>
> For A build a list while holding the lock and then release the pages
> later. In case of B we are the last remaining user of the slab so
> there is no need to take the listlock.
>
> After this patch all calls to the page allocator to free pages are
> done without holding any locks.
>
> V1->V2. Remove kfree. Avoid locking in free_partial. Drop slub_lock
> too.
>
> Signed-off-by: Christoph Lameter <cl@linux.com>
I'd like to merge this patch but it doesn't apply on top of Linus'
tree. Care to resend?
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-07-31 16:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 21:16 slub: [RFC] free slabs without holding locks Christoph Lameter
2011-07-07 19:04 ` Pekka Enberg
2011-07-14 0:25 ` David Rientjes
2011-07-14 14:20 ` Christoph Lameter
2011-07-14 15:35 ` slub: free slabs without holding locks (V2) Christoph Lameter
2011-07-31 16:19 ` Pekka Enberg [this message]
2011-08-01 15:30 ` 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=CAOJsxLF_BaPGx9CcYewKHs0FQdK_HfNXW5ptu2w9nAs47+GodQ@mail.gmail.com \
--to=penberg@kernel.org \
--cc=cl@linux.com \
--cc=linux-mm@kvack.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