From: Andi Kleen <andi@firstfloor.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Arjan van de Ven" <arjan@infradead.org>,
"Andi Kleen" <andi@firstfloor.org>,
"Ozan Çağlayan" <ozan@pardus.org.tr>,
"Alexey Dobriyan" <adobriyan@gmail.com>,
linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
"Ingo Molnar" <mingo@elte.hu>
Subject: Re: [PATCH] x86: suggest running a 64bit kernel on LM capable machines with plenty memory.
Date: Wed, 11 Mar 2009 13:38:45 +0100 [thread overview]
Message-ID: <20090311123845.GF11935@one.firstfloor.org> (raw)
In-Reply-To: <1236772885.8192.241.camel@laptop>
> Esp on x86_64 machines with >=4G of memory its insane to run i386-PAE.
Not sure I would apply insane to 4GB, but it definitely applies
to >= 16GB, likely >= 8GB. Enough known deadlocks in this case.
I would consider >=16GB on 32bit at least a kerneloops worthy condition.
Perhaps the warnings should vary in urgency. e.g. if it's >= 16GB and
not 2:2 split we know that the system will have problems and it should
strongly suggest, otherwise weakly.
Or perhaps it should be measured in percentage of mem_map
in lowmem?
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-03-11 12:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 11:04 [RFC] A simple way to determine if the kernel needs HIGHMEM64G to be able to use all the installed memory Ozan Çağlayan
2009-03-07 19:30 ` Alexey Dobriyan
2009-03-07 19:43 ` Ozan Çağlayan
2009-03-08 20:20 ` Andi Kleen
2009-03-09 13:42 ` [PATCH] x86: suggest running a 64bit kernel on LM capable machines with plenty memory Peter Zijlstra
2009-03-09 19:15 ` Andi Kleen
2009-03-10 9:37 ` Peter Zijlstra
2009-03-10 12:50 ` Andi Kleen
2009-03-10 13:21 ` Arjan van de Ven
2009-03-11 12:01 ` Peter Zijlstra
2009-03-11 12:38 ` Andi Kleen [this message]
2009-03-11 11:47 ` Ingo Molnar
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=20090311123845.GF11935@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=adobriyan@gmail.com \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ozan@pardus.org.tr \
--cc=peterz@infradead.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