From: Dave Hansen <haveblue@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-mm <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: resubmit - [PATCH 0/4] sparsemem intro patches
Date: Fri, 25 Mar 2005 12:43:43 -0800 [thread overview]
Message-ID: <1111783423.9691.65.camel@localhost> (raw)
Andrew, I noticed that these were dropped out of 2.6.12-mm1:
> -sparsemem-base-teach-discontig-about-sparse-ranges.patch
> -sparsemem-base-simple-numa-remap-space-allocator.patch
> -sparsemem-base-reorganize-page-flags-bit-operations.patch
> -sparsemem-base-early_pfn_to_nid-works-before-sparse-is-initialized.patch
>
> This was breaking compilation in various ways on various
> architectures.
> Returned to manufacturer.
I *think* those problems were caused by the actual sparsemem patches
that I posted for RFC, not the base "intro" patches. (I have fixes for
the problems that you were hitting with the RFC patches ready, too)
I've run these through a bunch of compile tests, including arm and alpha
with and without DISCONTIGMEM, and they seem OK. They also boot just
fine on a bunch of ppc64 and i386 configurations.
Can these go back into -mm?
----
The following four patches provide the last needed changes before the
introduction of sparsemem. For a more complete description of what this
will do, please see this patch:
http://www.sr71.net/patches/2.6.11/2.6.11-bk7-mhp1/broken-out/B-sparse-150-sparsemem.patch
or previous posts on the subject:
http://marc.theaimsgroup.com/?t=110868540700001&r=1&w=2
http://marc.theaimsgroup.com/?l=linux-mm&m=109897373315016&w=2
Three of these are i386-only, but one of them reorganizes the macros
used to manage the space in page->flags, and will affect all platforms.
There are analogous patches to the i386 ones for ppc64, ia64, and
x86_64, but those will be submitted by the normal arch maintainers.
The combination of the four patches has been test-booted on a variety of
i386 hardware, and compiled for ppc64, i386, and x86-64 with about 17
different .configs. It's also been runtime-tested on ia64 configs (with
more patches on top).
-- Dave
--
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:"aart@kvack.org"> aart@kvack.org </a>
reply other threads:[~2005-03-25 20:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1111783423.9691.65.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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