From: Andreas Dilger <adilger@turbolabs.com>
To: Eugene Chupkin <ace@credit.com>
Cc: linux-kernel@vger.kernel.org, tmeagher@credit.com
Subject: Re: 2.4.x ram issues?
Date: Wed, 13 Feb 2002 12:21:59 -0700 [thread overview]
Message-ID: <20020213122159.A16078@lynx.turbolabs.com> (raw)
In-Reply-To: <20020212213119.A25535@lynx.turbolabs.com> <Pine.LNX.4.10.10202131058110.683-100000@mail.credit.com>
In-Reply-To: <Pine.LNX.4.10.10202131058110.683-100000@mail.credit.com>; from ace@credit.com on Wed, Feb 13, 2002 at 11:05:32AM -0800
On Feb 13, 2002 11:05 -0800, Eugene Chupkin wrote:
> On Tue, 12 Feb 2002, Andreas Dilger wrote:
> > The other possibility with that much RAM is that the page tables are taking
> > up all of the low RAM. Andrea has a patch to put the page tables into
> > higmem in the recent -aa kernels.
>
> I got it, the 2.4.18pre2aa2/pte-highmem-5 but I can't seem to figure out
> what to patch this on, I tried patching it on to 2.2.17, 2.2.18-pre1,
> and 2.2.18-pre2. On all those I get a Hunk failed. Any feedback is
> appreciated.
You may need to use a whole bunch of -aa patches to get it to apply. In
general, the -aa tree is tuned for large machines such as yours, so you
are probably better off getting the whole thing.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2002-02-13 19:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 1:40 Eugene Chupkin
2002-02-13 2:00 ` Alan Cox
2002-02-13 2:52 ` Eugene Chupkin
2002-02-13 4:31 ` Andreas Dilger
2002-02-13 19:05 ` Eugene Chupkin
2002-02-13 19:21 ` Andreas Dilger [this message]
2002-02-13 20:33 ` Eugene Chupkin
2002-02-13 22:29 ` Mike Fedyk
2002-02-21 23:09 ` Eugene Chupkin
2002-02-14 19:13 ` Pavel Machek
2002-02-14 20:54 ` Eugene Chupkin
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=20020213122159.A16078@lynx.turbolabs.com \
--to=adilger@turbolabs.com \
--cc=ace@credit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tmeagher@credit.com \
/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
all inboxes | Powered by JetHome®