From: Michael Ellerman <michael@ellerman.id.au>
To: linuxppc64-dev@ozlabs.org
Cc: "Christopher Friesen" <cfriesen@nortel.com>,
linux-kernel@vger.kernel.org
Subject: Re: how to limit memory with 2.6.10 on ppc64 machine?
Date: Sat, 4 Feb 2006 11:54:02 +1100 [thread overview]
Message-ID: <200602041154.12710.michael@ellerman.id.au> (raw)
In-Reply-To: <43E3E55C.90504@nortel.com>
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]
On Sat, 4 Feb 2006 10:21, Christopher Friesen wrote:
> I'm running 2.6.10 on a ppc64 machine with 4GB of memory.
>
> We're debugging an issue and would like to try and see if disabling the
> U3 DART makes the problem go away. Unfortunately, this particular blade
> is unstable if not all the memory banks are populated.
>
> After some frustration I looked at the code and realized that the "mem="
> functionality is not supported for ppc64 on this particular kernel.
>
> Can anyone give me some advice on the simplest way to limit this thing
> to under 2GB of memory so that the DART is not allocated/used?
>
> Does anyone know when support for "mem=" was added? I know it is there
> in the current git version, but the "powerpc" consolidation means
> everything is all different now.
From memory (harhar) the mem= support was merged in 2.6.11, so the original
patch should _probably_ apply on a vanilla 2.6.10 tree, try it:
http://patchwork.ozlabs.org/linuxppc64/patch?id=724
cheers
--
Michael Ellerman
IBM OzLabs
email: michael:ellerman.id.au
inmsg: mpe:jabber.org
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-02-04 0:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 23:21 how to limit memory with 2.6.10 on ppc64 machine? Christopher Friesen
2006-02-04 0:54 ` Michael Ellerman [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=200602041154.12710.michael@ellerman.id.au \
--to=michael@ellerman.id.au \
--cc=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.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