All of lore.kernel.org
 help / color / mirror / Atom feed
From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: 2.6.0 test3 does not boot on ia64 NUMA
Date: Thu, 04 Sep 2003 19:11:55 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106270290013943@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106191285716253@msgid-missing>

On Thu, Sep 04, 2003 at 12:06:46PM -0700, Luck, Tony wrote:
> What are the remaining issues with sparse memory within a node?
> CONFIG_VIRTUAL_MEM_MAP should be able to cope with this without
> wasting memory on "struct page" for non-existent pages in the holes.

Yeah, that's what we're using the latest discontig patches.

> Presumably there are some bootmem bitmap size issues if the gaps
> within nodes are too huge.  But a few GB shouldn't be a problem (with
> a 16K page size, each GB of memory/hole only takes 8K of bitmap).

Right, until we get really huge holes, that'll be ok, and there are
already some optimizations to keep track of the last place a successful
bootmem allocation came from so that you don't keep walking through the
holes, which helped zx1 boots.

> Is there anything else that blows up?

Not that I know of...

> If not, then could we just drop the printk altogether?

Sure, sounds good to me.

Jesse

  parent reply	other threads:[~2003-09-04 19:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-26 15:39 2.6.0 test3 does not boot on ia64 NUMA Xavier Bru
2003-08-26 16:13 ` Martin Hicks
2003-08-28 16:38 ` Xavier Bru
2003-08-28 16:59 ` Martin Hicks
2003-08-29 16:41 ` Xavier Bru
2003-08-29 17:07 ` Martin Hicks
2003-09-01 12:36 ` Xavier Bru
2003-09-02 17:27 ` Xavier Bru
2003-09-04 18:31 ` Jesse Barnes
2003-09-04 19:06 ` Luck, Tony
2003-09-04 19:11 ` Jesse Barnes [this message]
2003-09-05  9:19 ` Xavier Bru
2003-09-08 19:08 ` Jesse Barnes

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-106270290013943@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 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.