All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: JBeulich@novell.com, andi@firstfloor.org, mingo@elte.hu,
	linux-kernel-owner@vger.kernel.org, hpa@zytor.com,
	tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: [GIT PATCH 2.6.30-rc5] x86,percpu: fix pageattr handling with remap allocator, take#2
Date: Fri, 15 May 2009 13:28:54 +0900	[thread overview]
Message-ID: <1242361739-21186-1-git-send-email-tj@kernel.org> (raw)

Hello,

Upon ack, please pull from the following git tree.

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

This is the second take of x86-percpu-fix-pageattr patchset.  Changes
from the last take[L] are...

* 0002 and renamed as per Jan's comment.

* 0003 updated accordingly.

* 0004 updated so that selection logic is left in individual setup
  functions.  This way is easier to add more complex selection logic.

* 0005 added.  This patch makes sure remap allocator doesn't consume
  too much of vmalloc space.  The cutoff is currently 20%.

This patchset contains the following five patches.

  0001-x86-prepare-setup_pcpu_remap-for-pageattr-fix.patch
  0002-x86-reorganize-cpa_process_alias.patch
  0003-x86-fix-pageattr-handling-for-remap-percpu-allocato.patch
  0004-x86-implement-percpu_alloc-kernel-parameter.patch
  0005-x86-ensure-percpu-remap-doesn-t-consume-too-much-vm.patch

and is on top of the current linux-2.6#master (45d44740).

Ingo, 0001-0003 are bug fixes and although 0004-0005 aren't exactly
bug fixes, I think it would be better to include them in 2.6.30.

diffstat follows.

 Documentation/kernel-parameters.txt |    6 +
 arch/x86/include/asm/percpu.h       |    9 +
 arch/x86/kernel/setup_percpu.c      |  199 +++++++++++++++++++++++++++---------
 arch/x86/mm/pageattr.c              |   63 +++++++----
 mm/percpu.c                         |   13 +-
 5 files changed, 218 insertions(+), 72 deletions(-)

Thanks.

--
tejun

             reply	other threads:[~2009-05-15  4:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-15  4:28 Tejun Heo [this message]
2009-05-15  4:28 ` [PATCH 1/5] x86: prepare setup_pcpu_remap() for pageattr fix Tejun Heo
2009-05-15  4:28 ` [PATCH 2/5] x86: reorganize cpa_process_alias() Tejun Heo
2009-05-15  9:35   ` [PATCH UPDATED " Tejun Heo
2009-05-15  4:28 ` [PATCH 3/5] x86: fix pageattr handling for remap percpu allocator Tejun Heo
2009-05-15  7:58   ` Jan Beulich
2009-05-15  8:18     ` Tejun Heo
2009-05-15  9:35   ` [PATCH UPDATED " Tejun Heo
2009-05-15  4:28 ` [PATCH 4/5] x86: implement percpu_alloc kernel parameter Tejun Heo
2009-05-15  8:04   ` Jan Beulich
2009-05-15  9:27     ` Tejun Heo
2009-05-15  4:28 ` [PATCH 5/5] x86: ensure percpu remap doesn't consume too much vmalloc space Tejun Heo
2009-05-15  9:36 ` [GIT PATCH 2.6.30-rc5] x86,percpu: fix pageattr handling with remap allocator, take#2 Tejun Heo
2009-05-15  9:52   ` [GIT PATCH 2.6.30-rc5] x86,percpu: fix pageattr handling withremap " Jan Beulich
     [not found]   ` <4A0D57920200007800001150@novell.com>
2009-05-15 10:08     ` Tejun Heo

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=1242361739-21186-1-git-send-email-tj@kernel.org \
    --to=tj@kernel.org \
    --cc=JBeulich@novell.com \
    --cc=andi@firstfloor.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel-owner@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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.