linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andy Whitcroft <apw@shadowen.org>,
	linux-mm@kvack.org, linux-arch@vger.kernel.org,
	Nick Piggin <npiggin@suse.de>, Mel Gorman <mel@csn.ul.ie>
Subject: Re: [PATCH 3/7] Generic Virtual Memmap support for SPARSEMEM
Date: Mon, 23 Jul 2007 12:36:18 -0700	[thread overview]
Message-ID: <20070723123618.4a25f902@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070714163319.GA14184@infradead.org>

On Sat, 14 Jul 2007 17:33:19 +0100
Christoph Hellwig <hch@infradead.org> wrote:
 
> It's not generic.  Most of it is under a maze of obscure config
> options. The patchset in it's current form is a complete mess of
> obscure ifefery and not quite generic code.  And it only adds new
> memory models without ripping old stuff out.  So while I really like
> the basic idea the patches need quite a lot more work until they're
> mergeable.

It is generic. If you would put the components into each arch then you
would needlessly duplicate code. In order to rip stuff out we first
need to have sparsemem contain all the features of discontig.

Then we can start to get rid of discontig and then we will be able to
reduce the number of memory models supported by sparsemem.

--
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:[~2007-07-23 19:36 UTC|newest]

Thread overview: 39+ 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 14:24   ` [PATCH] Bah, hoisted by my own petard. Below is an updated version 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 [this message]
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
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, Andrew Morton
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=20070723123618.4a25f902@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=apw@shadowen.org \
    --cc=hch@infradead.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