All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Schermerhorn <lee.schermerhorn@hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [PATCH 0/1] ia64:  numa emulation
Date: Thu, 20 Oct 2005 20:58:57 +0000	[thread overview]
Message-ID: <1129841937.6182.49.camel@localhost.localdomain> (raw)
In-Reply-To: <1129840588.6182.36.camel@localhost.localdomain>

On Thu, 2005-10-20 at 13:52 -0700, Chen, Kenneth W wrote:
> Lee Schermerhorn wrote on Thursday, October 20, 2005 1:36 PM
> > Also, because of interaction of max order and huge tlb fs [hard
> > coded HPAGE_SHIFT_DEFAULT], I disable hugetlbfs when numa emulation
> > is configured.
> 
> Hugetlbfs can still be safely enabled.  The only downside is system
> won't be able to reserve any hugetlb page with the default size. Maybe
> it is senseless, but no harm is done here by enabling it.

OK.  I wasn't sure, and didn't have need for hugetlbfs at the time, so I
just disabled it by default when emulation selected.  One could always
override that default.

> 
> 
> > Back around 2.6.10, I recall seeing discussion of dynamically sizing
> > hugetlbfs based on max order.  I haven't tracked this to see if it
> > went in.  But, if it did, one could reenable hugetlbfs and adapted
> > to the reduced max order automatically.
> 
> I have a patch does better than that.  We can change the hugetlb page
> size at run time.  I will clean up my patch and post it.
> 

Cool.  Sounds like a generic [!just ia64] patch, right?

Lee


  parent reply	other threads:[~2005-10-20 20:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-20 20:36 [PATCH 0/1] ia64: numa emulation Lee Schermerhorn
2005-10-20 20:52 ` Chen, Kenneth W
2005-10-20 20:58 ` Lee Schermerhorn [this message]
2005-10-20 21:47 ` Chen, Kenneth W

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=1129841937.6182.49.camel@localhost.localdomain \
    --to=lee.schermerhorn@hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.