linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: akpm@linux-foundation.org, Pekka Enberg <penberg@cs.helsinki.fi>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org, travis@sgi.com,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Vegard Nossum <vegard.nossum@gmail.com>
Subject: Re: [patch 5/7] x86_64: Support for cpu ops
Date: Thu, 6 Nov 2008 16:15:58 +0100	[thread overview]
Message-ID: <20081106151558.GB1644@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0811060907570.3595@quilx.com>

* Christoph Lameter <cl@linux-foundation.org> wrote:

> On Thu, 6 Nov 2008, Ingo Molnar wrote:
> 
> > hm, what happened to the rebase-PDA-to-percpu-area optimization 
> > patches you guys were working on? I remember there was some 
> > binutils flakiness - weird crashes and things like that. Did you 
> > ever manage to stabilize it? It would be sad if only 32-bit could 
> > take advantage of the optimized ops.
> 
> I thought that was in your tree? I saw a conflict in -next with the 
> zero based stuff a couple of weeks ago. Mike is working on that 
> AFAICT.

No, what's in tip/core/percpu is not the PDA patches:

 f8d90d9: percpu: zero based percpu build error on s390
 cfcfdff: Merge branch 'linus' into core/percpu
 d379497: Zero based percpu: infrastructure to rebase the per cpu area to zero
 b3a0cb4: x86: extend percpu ops to 64 bit

But it's not actually utilized on x86. AFAICS you guys never came back 
with working patches for that (tip/x86/percpu is empty currently), and 
now i see something related on lkml on a separate track not Cc:-ed to 
the x86 folks so i thought i'd ask whether more coordination is 
desired here.

So ... what's the merge plan here? I like your fundamental idea, it's 
a nice improvement in a couple of areas and i'd like to help out make 
it happen. Also, the new per-cpu allocator would be nice for the 
sparseirq code.

	Ingo

--
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>

  reply	other threads:[~2008-11-06 15:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-05 23:16 [patch 0/7] cpu alloc stage 2 Christoph Lameter
2008-11-05 23:16 ` [patch 1/7] Increase default reserve percpu area Christoph Lameter
2008-11-05 23:16 ` [patch 2/7] cpu alloc: Use in slub Christoph Lameter
2008-11-05 23:16 ` [patch 3/7] cpu alloc: Remove slub fields Christoph Lameter
2008-11-05 23:16 ` [patch 4/7] cpu ops: Core piece for generic atomic per cpu operations Christoph Lameter
2008-11-06  3:58   ` Dave Chinner
2008-11-06 15:05     ` Christoph Lameter
2008-11-05 23:16 ` [patch 5/7] x86_64: Support for cpu ops Christoph Lameter
2008-11-06  7:12   ` Ingo Molnar
2008-11-06 15:08     ` Christoph Lameter
2008-11-06 15:15       ` Ingo Molnar [this message]
2008-11-06 15:44         ` Mike Travis
2008-11-06 16:27           ` Christoph Lameter
2008-11-06 16:11         ` Christoph Lameter
2008-11-05 23:16 ` [patch 6/7] VM statistics: Use CPU ops Christoph Lameter
2008-11-05 23:16 ` [patch 7/7] cpu alloc: page allocator conversion Christoph Lameter
2008-11-06  2:52   ` KOSAKI Motohiro
2008-11-06 15:04     ` Christoph Lameter
2008-11-07  0:37       ` KOSAKI Motohiro
2008-11-07 18:43         ` Christoph Lameter
2008-11-11  6:10           ` KOSAKI Motohiro
2008-11-12  2:02             ` Christoph Lameter
2008-11-11 23:56 ` [patch 0/7] cpu alloc stage 2 Andrew Morton
2008-11-12  0:28   ` Christoph Lameter
2008-11-12  6:57 ` Stephen Rothwell
2008-11-12 20:07   ` Christoph Lameter
2008-11-12 23:35     ` Stephen Rothwell
2008-11-13 14:28       ` Christoph Lameter
2008-11-13 21:09         ` 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=20081106151558.GB1644@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=sfr@canb.auug.org.au \
    --cc=travis@sgi.com \
    --cc=vegard.nossum@gmail.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