From: "Martin J. Bligh" <mbligh@mbligh.org>
To: christoph <christoph@scalex86.org>,
Dave Hansen <haveblue@us.ibm.com>,
Andy Whitcroft <apw@shadowen.org>
Cc: linux-mm <linux-mm@kvack.org>,
shai@scalex86.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Factor in buddy allocator alignment requirements in node memory alignment
Date: Mon, 16 May 2005 13:51:36 -0700 [thread overview]
Message-ID: <731890000.1116276696@flay> (raw)
In-Reply-To: <Pine.LNX.4.62.0505161240240.13692@ScMPusgw>
--On Monday, May 16, 2005 12:43:17 -0700 christoph <christoph@scalex86.org> wrote:
> On Mon, 16 May 2005, Dave Hansen wrote:
>
>> On Mon, 2005-05-16 at 12:05 -0700, christoph wrote:
>> > Memory for nodes on i386 is currently aligned on 2 MB boundaries.
>> > However, the buddy allocator needs pages to be aligned on
>> > PAGE_SIZE << MAX_ORDER which is 8MB if MAX_ORDER = 11.
>>
>> Why do you need this? Are you planning on allowing NUMA KVA remap pages
>> to be handed over to the buddy allocator? That would be a major
>> departure from what we do now, and I'd be very interested in seeing how
>> that is implemented before a infrastructure for it goes in.
>
> Because the buddy allocator is complaining about wrongly allocated zones!
>
> in page_alloc.c:
>
> static void __init free_area_init_core(struct pglist_data *pgdat,
> unsigned long *zones_size, unsigned long *zholes_size)
> {
> ...
>
> const unsigned long zone_required_alignment = 1UL << (MAX_ORDER-1);
>
> ...
>
> if ((zone_start_pfn) & (zone_required_alignment-1))
> printk(KERN_CRIT "BUG: wrong zone alignment, it will crash\n");
IIRC, we decided that warning was worthless ... and I *think* Andy fixed
it to do non-aligned zones, though it might have been someone else. Andy,
can you remember what you did to fix this up?
M.
--
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>
next prev parent reply other threads:[~2005-05-16 20:51 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 [this message]
2005-05-17 12:25 ` Andy Whitcroft
2005-05-17 17:19 ` christoph
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=731890000.1116276696@flay \
--to=mbligh@mbligh.org \
--cc=apw@shadowen.org \
--cc=christoph@scalex86.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