All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	lkml <linux-kernel@vger.kernel.org>
Cc: David Howells <dhowells@redhat.com>,
	graff yang <graff.yang@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	uclinux-dist-devel@blackfin.uclinux.org,
	Sonic Zhang <sonic.adi@gmail.com>,
	Christoph Lameter <cl@linux-foundation.org>
Subject: [GIT PULL] percpu for v2.6.35-rc1
Date: Tue, 18 May 2010 18:10:20 +0200	[thread overview]
Message-ID: <4BF2BBEC.7010506@kernel.org> (raw)

Hello, Linus.

Please pull from the following branch to receive percpu changes for
2.6.35-rc1.

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

There are six commits.  One is to add sparse annotation to ia64.  All
the others are to implement nommu percpu support.  blackfin does SMP
w/o mmu and thus requires percpu allocator which doesn't make use of
remapping in the vmalloc area.  Percpu chunk [de]allocation and
[de]population code paths are factored out and nommu simply allocates
contiguous kernel memory for each unit.

Thanks.

Tejun Heo (6):
      percpu: factor out pcpu_addr_in_first/reserved_chunk() and update per_cpu_ptr_to_phys()
      percpu: reorganize chunk creation and destruction
      percpu: misc preparations for nommu support
      percpu: move vmalloc based chunk management into percpu-vm.c
      percpu: implement kernel memory based chunk allocation
      ia64: add sparse annotation to __ia64_per_cpu_var()

 arch/ia64/include/asm/percpu.h |    5 +-
 mm/percpu-km.c                 |  104 +++++++
 mm/percpu-vm.c                 |  451 +++++++++++++++++++++++++++++++
 mm/percpu.c                    |  585 ++++++++--------------------------------
 4 files changed, 671 insertions(+), 474 deletions(-)
 create mode 100644 mm/percpu-km.c
 create mode 100644 mm/percpu-vm.c

--
tejun

                 reply	other threads:[~2010-05-18 16:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4BF2BBEC.7010506@kernel.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=graff.yang@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sonic.adi@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=uclinux-dist-devel@blackfin.uclinux.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.