public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: discontig patch question
Date: Mon, 10 Nov 2003 19:08:31 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106849134202103@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106847971018555@msgid-missing>

On Mon, Nov 10, 2003 at 12:34:47PM -0600, Van Maren, Kevin wrote:
> > Yeah, but 1UL<<MAX_ORDER will always be page aligned, right?
> 
> Only if MAX_ORDER >= PAGE_SHIFT.
> 
> But page alignment isn't the question: it is already aligned to
> the 16MB or 64MB granules.

Right.  Spaced out there for a minute...

> But you are saying that the address doesn't have to be as strict:
> even if allocating 2^MAX_ORDER _pages_, the start doesn't have to
> be aligned at a natural (PAGE_SIZE<<MAX_ORDER) boundary, and that
> we can change the ORDERROUNDDOWN to not be as aggressive.

Well, strictly speaking I don't think start _has_ to align on those
conditions, but the hugetlb stuff may that it does (I haven't looked).

> But then it also makes sense to have a smaller MAX_ORDER when not
> using 4GB hugepages?  I'm happy with <= 256MB hugepages with 16GB ram,
> so I guess I'd rather MAX_ORDER was normally smaller, and increased
> only with very large hugepage pages.

That makes sense to me.  It seems like FORCE_MAX_ZONEORDER should depend
on HUGETLB_PAGE_SIZE_* so that we don't apply unnecessary alignment
constraints.  Of course, there's probably something I'm missing, Rohit
might know more.

Jesse

  parent reply	other threads:[~2003-11-10 19:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-10 15:52 discontig patch question Van Maren, Kevin
2003-11-10 17:23 ` Jesse Barnes
2003-11-10 17:38 ` Van Maren, Kevin
2003-11-10 17:56 ` Jesse Barnes
2003-11-10 18:02 ` Seth, Rohit
2003-11-10 18:34 ` Van Maren, Kevin
2003-11-10 19:08 ` Jesse Barnes [this message]
2003-11-10 19:10 ` Jesse Barnes
2003-11-10 20:20 ` Seth, Rohit
2003-11-12 18:14 ` Van Maren, Kevin

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=marc-linux-ia64-106849134202103@msgid-missing \
    --to=jbarnes@sgi.com \
    --cc=linux-ia64@vger.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