From: Christoph Lameter <cl@gentwo.org>
To: David Rientjes <rientjes@google.com>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
Yinghai Lu <yinghai@kernel.org>, Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>, Rik van Riel <riel@redhat.com>,
Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
Linux MM <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] x86: numa: drop ZONE_ALIGN
Date: Fri, 13 Jun 2014 10:47:27 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1406131045340.913@gentwo.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1406111553430.27885@chino.kir.corp.google.com>
On Wed, 11 Jun 2014, David Rientjes wrote:
> > > Yes, but the question is: why?
> >
> > zones need to be aligned so that the huge pages order and other page
> > orders allocated from the page allocator are at their "natural alignment".
> > Otherwise huge pages cannot be mapped properly and various I/O devices
> > may encounter issues if they rely on the natural alignment.
> >
>
> Any reason not to align to HUGETLB_PAGE_ORDER on x86 instead of
> ZONE_ALIGN?
if MAX_ORDER = Hugetlb order then no issue.
However, if there are devices that require larger order pages (dont know
if such devices exist) then there may be an issue. SGI UV DMA engine,
graphics or some other device?
--
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:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2014-06-13 15:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 22:14 Luiz Capitulino
2014-06-08 22:25 ` David Rientjes
2014-06-09 18:43 ` Luiz Capitulino
2014-06-09 21:57 ` David Rientjes
2014-06-10 3:19 ` Luiz Capitulino
2014-06-10 22:10 ` David Rientjes
2014-06-11 2:21 ` Luiz Capitulino
2014-06-09 1:29 ` Yinghai Lu
2014-06-09 19:03 ` Luiz Capitulino
2014-06-09 22:13 ` Yinghai Lu
2014-06-11 13:23 ` Luiz Capitulino
2014-06-11 13:58 ` Christoph Lameter
2014-06-11 22:54 ` David Rientjes
2014-06-13 15:47 ` Christoph Lameter [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=alpine.DEB.2.10.1406131045340.913@gentwo.org \
--to=cl@gentwo.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.org \
--cc=yinghai@kernel.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