From: Mike Fedyk <mfedyk@matchmail.com>
To: Eugene Chupkin <ace@credit.com>
Cc: Andreas Dilger <adilger@turbolabs.com>,
linux-kernel@vger.kernel.org, tmeagher@credit.com,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Andrea Arcangeli <andrea@suse.de>
Subject: Re: 2.4.x ram issues?
Date: Wed, 13 Feb 2002 14:29:42 -0800 [thread overview]
Message-ID: <20020213222942.GB335@matchmail.com> (raw)
In-Reply-To: <20020213122159.A16078@lynx.turbolabs.com> <Pine.LNX.4.10.10202131229480.683-100000@mail.credit.com>
In-Reply-To: <Pine.LNX.4.10.10202131229480.683-100000@mail.credit.com>
> On Wed, 13 Feb 2002, Andreas Dilger wrote:
> > 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.
> >
>
On Wed, Feb 13, 2002 at 12:33:37PM -0800, Eugene Chupkin wrote:
> Whola!!! This fixed my problem. CONFIG_HIGHIO did it. So my kernel is lets
> see here... 2.4.18pre2aa2+pte-highmem-5. I hope this will be included in
> the 2.4.18 final. Thanks for all your help.
>
I don't think that will happen. pte-highmem is relatively new code, and
needs more testing before it goes into 2.4. Hugh, and Andrea fixed some
potential problems with it recently, so hopefully most of it is ironed out
now.
Also, Andrea and Marcelo (CCed) need to take some time to merge some of -aa into
2.4-pre. Any comments guys? We're all watching and waiting to see more
merging in this area...
Mike
next prev parent reply other threads:[~2002-02-13 22:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 1:40 2.4.x ram issues? 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
2002-02-13 20:33 ` Eugene Chupkin
2002-02-13 22:29 ` Mike Fedyk [this message]
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=20020213222942.GB335@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=ace@credit.com \
--cc=adilger@turbolabs.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--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