From: christoph <christoph@scalex86.org>
To: Dave Hansen <haveblue@us.ibm.com>
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:12:11 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.62.0505161308010.25748@ScMPusgw> (raw)
In-Reply-To: <1116277014.1005.113.camel@localhost>
On Mon, 16 May 2005, Dave Hansen wrote:
> > > Do you know which pieces of code actually break if the alignment doesn't
> > > meet what that warning says?
> >
> > I have seen nothing break but 4 MB allocations f.e. will not be allocated
> > on a 4MB boundary with a 2 MB zone alignment. The page allocator always
> > returnes properly aligned pages but 4MB allocations are an exception?
>
> I wasn't aware there was an alignment exception in the allocator for 4MB
> pages. Could you provide some examples?
I never said that there was an aligment exception. The special case for
4MB pages is created by the failure to properly align the zones in
discontig.c.
But may be that is okay? Then we just need to remove the lines that
detect the misalignment in the page allocator.
--
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:12 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 [this message]
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
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.0505161308010.25748@ScMPusgw \
--to=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