All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: mingo@elte.hu, rusty@rustcorp.com.au, tglx@linutronix.de,
	x86@kernel.org, linux-kernel@vger.kernel.org, hpa@zytor.com,
	npiggin@suse.de, akpm@linux-foundation.org
Subject: [GIT PULL] percpu: finer grained locking
Date: Sat,  7 Mar 2009 00:54:39 +0900	[thread overview]
Message-ID: <1236354883-25063-1-git-send-email-tj@kernel.org> (raw)


Hello,

Please pull from the following git vector.

  git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git tj-percpu

This patchset makes locking in dynamic percpu allocator finer grained
to break deadlock[1] and allow atomic free.

This patchset is on top of the current x86/core/percpu[2] contains the
following patches.

 0001-percpu-replace-pcpu_realloc-with-pcpu_mem_alloc.patch
 0002-percpu-move-chunk-area-map-extension-out-of-area-al.patch
 0003-percpu-move-fully-free-chunk-reclamation-into-a-wor.patch
 0004-percpu-finer-grained-locking-to-break-deadlock-and.patch

0001-0003 prepare for finer grained locking.  0004 implements it.

Diffstat follows.

 mm/percpu.c |  365 ++++++++++++++++++++++++++++++++++++++++--------------------
 1 file changed, 245 insertions(+), 120 deletions(-)

Thanks.

--
tejun

[1] http://thread.gmane.org/gmane.linux.kernel/802384
[2] 6b19b0c2400437a3c10059ede0e59b517092e1bd

             reply	other threads:[~2009-03-06 15:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06 15:54 Tejun Heo [this message]
2009-03-06 15:54 ` [PATCH 1/4] percpu: replace pcpu_realloc() with pcpu_mem_alloc() and pcpu_mem_free() Tejun Heo
2009-03-06 15:54 ` [PATCH 2/4] percpu: move chunk area map extension out of area allocation Tejun Heo
2009-03-06 15:54 ` [PATCH 3/4] percpu: move fully free chunk reclamation into a work Tejun Heo
2009-03-06 15:54 ` [PATCH 4/4] percpu: finer grained locking to break deadlock and allow atomic free Tejun Heo
2009-03-07  5:49   ` [PATCH UPDATED " Tejun Heo
2009-03-08 10:20     ` Ingo Molnar

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=1236354883-25063-1-git-send-email-tj@kernel.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=npiggin@suse.de \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    --cc=x86@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.