From: christoph <christoph@scalex86.org>
To: linux-mm@kvack.org
Cc: akpm@osdl.org, Andy Whitcroft <apw@shadowen.org>,
haveblue@us.ibm.com, linux-kernel@vger.kernel.org,
shai@scalex86.org
Subject: Re: [PATCH] Factor in buddy allocator alignment requirements in node memory alignment
Date: Tue, 17 May 2005 10:19:58 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.62.0505171018560.2872@ScMPusgw> (raw)
In-Reply-To: <E1DY18K-0002dJ-KM@pinky.shadowen.org>
On Tue, 17 May 2005, Andy Whitcroft wrote:
> Andrew, please consider this patch for -mm.
I agree. Forget about my patch and include this one.
> Originally __free_pages_bulk used the relative page number within
> a zone to define its buddies. This meant that to maintain the
> "maximally aligned" requirements (that an allocation of size N will
> be aligned at least to N physically) zones had to also be aligned to
> 1<<MAX_ORDER pages. When __free_pages_bulk was updated to use the
> relative page frame numbers of the free'd pages to pair buddies this
> released the alignment constraint on the 'left' edge of the zone.
> This allows _either_ edge of the zone to contain partial MAX_ORDER
> sized buddies. These simply never will have matching buddies and
> thus will never make it to the 'top' of the pyramid.
>
> The patch below removes a now redundant check ensuring that the
> mem_map was aligned to MAX_ORDER.
>
> Signed-off-by: Andy Whitcroft <apw@shadowen.org>
>
> diffstat free_area_init_core-remove-bogus-warning
> ---
> page_alloc.c | 4 ----
> 1 files changed, 4 deletions(-)
>
> diff -X /home/apw/brief/lib/vdiff.excl -rupN reference/mm/page_alloc.c current/mm/page_alloc.c
> --- reference/mm/page_alloc.c
> +++ current/mm/page_alloc.c
> @@ -1942,7 +1942,6 @@ static void __init free_area_init_core(s
> unsigned long *zones_size, unsigned long *zholes_size)
> {
> unsigned long i, j;
> - const unsigned long zone_required_alignment = 1UL << (MAX_ORDER-1);
> int cpu, nid = pgdat->node_id;
> unsigned long zone_start_pfn = pgdat->node_start_pfn;
>
> @@ -2033,9 +2032,6 @@ static void __init free_area_init_core(s
> zone->zone_mem_map = pfn_to_page(zone_start_pfn);
> zone->zone_start_pfn = zone_start_pfn;
>
> - if ((zone_start_pfn) & (zone_required_alignment-1))
> - printk(KERN_CRIT "BUG: wrong zone alignment, it will crash\n");
> -
> memmap_init(size, nid, j, zone_start_pfn);
>
> zonetable_add(zone, nid, j, zone_start_pfn, size);
>
>
>
--
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>
prev parent reply other threads:[~2005-05-17 17:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 19:05 christoph
2005-05-16 20:14 ` Dave Hansen
2005-05-16 19:43 ` christoph
2005-05-16 20:47 ` Dave Hansen
2005-05-16 19:55 ` christoph
2005-05-16 20:56 ` Dave Hansen
2005-05-16 20:12 ` christoph
2005-05-16 21:06 ` Martin J. Bligh
2005-05-17 13:12 ` Andrea Arcangeli
2005-05-17 14:16 ` Andy Whitcroft
2005-05-16 20:51 ` Martin J. Bligh
2005-05-17 12:25 ` Andy Whitcroft
2005-05-17 17:19 ` christoph [this message]
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.62.0505171018560.2872@ScMPusgw \
--to=christoph@scalex86.org \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shai@scalex86.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