From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Yinghai Lu <yinghai@kernel.org>, Tejun Heo <tj@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: 32bit panic on 4 sockets
Date: Wed, 4 Mar 2009 12:07:08 +0100 [thread overview]
Message-ID: <20090304110708.GA4645@elte.hu> (raw)
In-Reply-To: <1236163190.5330.7091.camel@laptop>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Wed, 2009-03-04 at 11:34 +0100, Ingo Molnar wrote:
> > * Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > > On Tue, 2009-03-03 at 22:57 -0800, Yinghai Lu wrote:
> > > > On Tue, Mar 3, 2009 at 6:05 PM, Tejun Heo <tj@kernel.org> wrote:
> > > > > Looks like a genuine bootmem bug. Cc'ing Johannes and
> > > > > quoting whole body.
> > > >
> > > > it is x86 32bit numa code problem. it assume bootmem will
> > > > sit on first node only.
> > >
> > > Seems a bit daft to run a 32bit kernel on such a machine.. at
> > > some point we should just give up and not push this 32 bit
> > > madness any further.
> >
> > it works just fine on a lot of systems - and since we keep
> > unifying a lot of these codepaths we are better off keeping it
> > all working.
>
> Sure, but eg. running with 16GB on a 32bit system just isn't
> going to work well. Same with large cpu-count, at some point
> you might be able to boot, but not much else.
Sure.
Ingo
prev parent reply other threads:[~2009-03-04 11:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86802c440903031458p4a72f8c8x6f91e9f58ac6bc26@mail.gmail.com>
2009-03-04 1:51 ` 32bit panic on 4 sockets Yinghai Lu
2009-03-04 2:05 ` Tejun Heo
2009-03-04 3:58 ` Yinghai Lu
2009-03-04 6:57 ` Yinghai Lu
2009-03-04 8:34 ` Peter Zijlstra
2009-03-04 10:34 ` Ingo Molnar
2009-03-04 10:39 ` Peter Zijlstra
2009-03-04 11:07 ` Ingo Molnar [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=20090304110708.GA4645@elte.hu \
--to=mingo@elte.hu \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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 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.