From: Mitch Sako <msako@cadence.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: -aa 3.5GB Patch Questions
Date: Fri, 09 Aug 2002 12:35:05 -0700 [thread overview]
Message-ID: <3D541969.48A1D9E3@cadence.com> (raw)
I've been using Andrea's 2.4.18rc4aa1 patches applied to a generic
2.4.18 kernel running on Intel 32-bit machines with 4GB of memory and
usually some sort of Serversorks chipset with 1-2 CPUs of various speeds
with great success for almost 6 months now. The primary base has been a
SuSE 7.2 distro but others are now being tried, including Slackware 8.1
and RH 7.[23]. The principal reason for this was to use the
00_3.5G-address-space-4 feature. I apply all patches in the directory
and have not seen a kernel failure yet with thousands of hours of "big
process" CPU time logged across many machines. I consider this to be a
pretty stable combination of kernel and patches for what I need.
RH's 2.96 gcc compiles fine but blows up or slows to a crawl (not
unexpected) when big jobs are run and the machine starts paging. I've
fixed this by putting a 2.95.3 gcc on the machine. I'll leave the
editorial comments about 2.96-RH to others.
I'm trying to write some sanitized procedures which will allow me to
pass this on to others. Non-2.96 distros (everyone except RH and
Mandrake, AFAIK) have run fine without issues, mainly because they have
a pretty stable 2.95 compiler included.
I will assume that a gcc 2.95 retrofit is required to make the -aa
patches work on RH 7.[23].
What's the correct way to retrofit a 2.95.3 compiler onto an RH 7.[23]
distro?
Is it OK to just load it into /usr/local and build it?
Does it require 'make bootstrap' to be entirely santized?
Are there other GNU packages that I should be including with the gcc
retrofit?
-ms
next reply other threads:[~2002-08-09 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 19:35 Mitch Sako [this message]
2002-08-09 20:06 ` -aa 3.5GB Patch Questions J Sloan
2002-08-12 19:01 ` Mitch Sako
2002-08-13 7:30 ` J Sloan
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=3D541969.48A1D9E3@cadence.com \
--to=msako@cadence.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox