From: Andi Kleen <ak@suse.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Nick Piggin <nickpiggin@yahoo.com.au>,
Marcelo Tosatti <marcelo@kvack.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Paul Jackson <pj@sgi.com>,
dgc@sgi.com, Ravikiran G Thirumalai <kiran@scalex86.org>,
Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
jes@sgi.com, Adam Litke <agl@us.ibm.com>,
Mel Gorman <mel@csn.ul.ie>,
steiner@sgi.com, Peter Zijlstra <a.p.zijlstra@chello.nl>,
akpm@osdl.org
Subject: Re: Agenda for NUMA BOF @OLS & NUMA paper
Date: Tue, 11 Jul 2006 08:22:52 +0200 [thread overview]
Message-ID: <200607110822.53711.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0607101146170.5556@schroedinger.engr.sgi.com>
On Monday 10 July 2006 21:22, Christoph Lameter wrote:
> Here is a one liner for each subject that may be useful to discuss. I'd be
> interested in hearing if there are any other issues that would need our
> attention or maybe some of these are not that important (Probably too many
> subjects already ...). Maybe this thread will allow those who will not be
> at the OLS to give us some imput.
Sounds reasonable, although it would be a lot of things to discuss.
Ok most of A doesn't seem to be directly NUMA related.
Does B mean you want to work on that? My impression was always
that doing it automatically in the kernel was more a deadend.
-Andi
--
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>
next prev parent reply other threads:[~2006-07-11 6:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 19:22 Christoph Lameter
2006-07-10 19:31 ` Jan-Benedict Glaw
2006-07-10 19:45 ` Christoph Lameter
2006-07-11 6:22 ` Andi Kleen [this message]
2006-07-11 15:43 ` 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=200607110822.53711.ak@suse.de \
--to=ak@suse.de \
--cc=Lee.Schermerhorn@hp.com \
--cc=a.p.zijlstra@chello.nl \
--cc=agl@us.ibm.com \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=dgc@sgi.com \
--cc=jes@sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcelo@kvack.org \
--cc=mel@csn.ul.ie \
--cc=nickpiggin@yahoo.com.au \
--cc=pj@sgi.com \
--cc=steiner@sgi.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