From: Christoph Lameter <clameter@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-arch@vger.kernel.org,
Andy Whitcroft <apw@shadowen.org>, Nick Piggin <npiggin@suse.de>,
Mel Gorman <mel@csn.ul.ie>
Subject: Re: [PATCH 0/7] Sparsemem Virtual Memmap V5
Date: Fri, 13 Jul 2007 11:23:20 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0707131116080.22727@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070713104044.0d090c79.akpm@linux-foundation.org>
On Fri, 13 Jul 2007, Andrew Morton wrote:
> It would be nice to see a bit of spirited reviewing from the affected arch
> maintainers and mm people...
That was already done a long time ago. Maybe you do not remember it.
See
http://marc.info/?l=linux-kernel&m=117556067909158&w=2
http://marc.info/?l=linux-kernel&m=117598342420719&w=2
http://marc.info/?l=linux-kernel&m=117541139915535&w=2
http://marc.info/?l=linux-kernel&m=116556142519461&w=2
> There's already an enormous amount of mm stuff banked up and it looks like
> I get to hold onto a lot of that until 2.6.24. We seem to be spending too
> little time on the first 90% of new stuff and too little time on the last
> 10% of existing stuff.
Well without this we cannot perform the cleanup of the miscellaneous
memory models around. The longer this is held up the longer the discontig
etc will stay in the tree with all the associated #ifdeffery.
next prev parent reply other threads:[~2007-07-13 18:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 13:34 [PATCH 0/7] Sparsemem Virtual Memmap V5 Andy Whitcroft
2007-07-13 13:35 ` [PATCH 1/7] sparsemem: clean up spelling error in comments Andy Whitcroft
2007-07-13 13:35 ` [PATCH 2/7] sparsemem: record when a section has a valid mem_map Andy Whitcroft
2007-07-13 13:36 ` [PATCH 3/7] Generic Virtual Memmap support for SPARSEMEM Andy Whitcroft
2007-07-13 14:51 ` KAMEZAWA Hiroyuki
2007-07-13 22:42 ` Christoph Lameter
2007-07-13 23:12 ` KAMEZAWA Hiroyuki
2007-07-13 23:17 ` Christoph Lameter
2007-07-13 23:25 ` KAMEZAWA Hiroyuki
2007-07-14 15:20 ` Christoph Hellwig
2007-07-14 16:06 ` Christoph Lameter
2007-07-14 16:33 ` Christoph Hellwig
2007-07-23 19:36 ` Christoph Lameter
2007-07-30 14:39 ` Andy Whitcroft
2007-07-30 18:35 ` Christoph Lameter
2007-07-13 13:36 ` [PATCH 4/7] x86_64: SPARSEMEM_VMEMMAP 2M page size support Andy Whitcroft
2007-07-19 23:25 ` Andrew Morton
2007-07-13 13:37 ` [PATCH 5/7] IA64: SPARSEMEM_VMEMMAP 16K " Andy Whitcroft
2007-07-13 13:37 ` [PATCH 6/7] SPARC64: SPARSEMEM_VMEMMAP support Andy Whitcroft
2007-07-13 17:00 ` Christoph Lameter
2007-07-13 13:38 ` [PATCH 7/7] ppc64: " Andy Whitcroft
2007-07-13 17:04 ` [PATCH 0/7] Sparsemem Virtual Memmap V5 Christoph Lameter
2007-07-13 17:40 ` Andrew Morton
2007-07-13 18:23 ` Christoph Lameter [this message]
2007-07-14 8:57 ` Russell King
2007-07-14 15:10 ` Christoph Lameter
2007-07-14 17:16 ` Russell King
2007-07-13 20:08 ` Roman Zippel
2007-07-13 22:02 ` Luck, Tony
2007-07-13 22:21 ` Christoph Lameter
2007-07-13 22:37 ` Luck, Tony
2007-07-13 22:54 ` Christoph Lameter
2007-07-13 23:27 ` KAMEZAWA Hiroyuki
2007-07-13 23:28 ` Christoph Lameter
2007-07-14 8:49 ` Nick Piggin
2007-07-14 15:07 ` Christoph Lameter
2007-07-13 22:43 ` David Miller
2007-07-26 8:05 ` Paul Mundt
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=Pine.LNX.4.64.0707131116080.22727@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=npiggin@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).