From: Andy Whitcroft <apw@shadowen.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>
Cc: linux-mm@kvack.org, linux-arch@vger.kernel.org,
Nick Piggin <npiggin@suse.de>,
Christoph Lameter <clameter@sgi.com>, Mel Gorman <mel@csn.ul.ie>,
Andy Whitcroft <apw@shadowen.org>
Subject: [PATCH 0/5] vmemmap updates to V7
Date: Fri, 10 Aug 2007 15:40:01 +0100 [thread overview]
Message-ID: <exportbomb.1186756801@pinky> (raw)
Following this email are a five patches which represent the second
batch of feedback on version V5. These represent a significant
simplification in the configuration options. There is still the
issue of the contents of memory_model.h to deal with, will look at
that next.
The thrust of this set of changes is to standardise the architecture
interface to vmemmap at the vmemmap_populate() function. All
architectures implementing this sparsemem variant must implement
this function. As part of this sparsemem offers several vmemmap
related helper functions to help initialise PUD, PGD, PMD and
PTE pages. It also offers a standard basepage initialiser.
vmemmap-generify-initialisation-via-helpers
conversion of the main infrastructure over to a helper based
system. General helpers for initialising pte pages are supplied,
plus a general helper for architectures using base pages.
vmemmap-x86_64-convert-to-new-helper-based-initialisation
vmemmap-ppc64-convert-to-new-config-options
vmemmap-sparc64-convert-to-new-config-options
vmemmap-ia64-convert-to-new-helper-based-initialisation
conversion of each of the supported architectures to the new helper
system. These remain broken out in the expectation that they would
merge with the main architecture implementations in -mm.
All against 2.6.23-rc2-mm2, in addition to the patches already there.
Again, they are split by architecture as I am assuming they will
slot into the current vmemmap stack before merging up. They are
not bisectable otherwise.
Andrew please consider for -mm.
-apw
next reply other threads:[~2007-08-10 14:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 14:40 Andy Whitcroft [this message]
2007-08-10 14:40 ` [PATCH 1/5] vmemmap: generify initialisation via helpers Andy Whitcroft
2007-08-10 17:56 ` Christoph Lameter
2007-08-15 14:54 ` Andy Whitcroft
2007-08-10 14:40 ` [PATCH 2/5] vmemmap x86_64: convert to new helper based initialisation Andy Whitcroft
2007-08-10 14:41 ` [PATCH 3/5] vmemmap ppc64: convert to new config options Andy Whitcroft
2007-08-10 14:41 ` [PATCH 4/5] vmemmap sparc64: " Andy Whitcroft
2007-08-10 14:41 ` [PATCH 5/5] vmemmap ia64: convert to new helper based initialisation Andy Whitcroft
2007-08-10 18:01 ` 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=exportbomb.1186756801@pinky \
--to=apw@shadowen.org \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--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;
as well as URLs for NNTP newsgroup(s).