From: Robert Love <rml@tech9.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Robert L. Harris" <Robert.L.Harris@rdlg.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Compiling options?
Date: 25 Mar 2003 13:38:19 -0500 [thread overview]
Message-ID: <1048617499.1486.334.camel@phantasy.awol.org> (raw)
In-Reply-To: <1048621636.28496.32.camel@irongate.swansea.linux.org.uk>
On Tue, 2003-03-25 at 14:47, Alan Cox wrote:
> If your boxes range from PII through to AMD duron build for 686, but the
> basic theory is the same.
>
> A 386 kernel really hurts later CPUs
> A 486 kernel is generally fine
> A 686 kernel speeds stuff up a little more
Should add that a 586 kernel is horrid on 686 and Athlon machines - the
scheduling is worlds apart. Use it only on true 586 machines.
If you need a common denominator, go with 486 as Alan pointed out. In
your case 686 seems safe and sane, though.
Robert Love
prev parent reply other threads:[~2003-03-25 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 18:03 Robert L. Harris
2003-03-25 18:16 ` Dave Jones
2003-03-25 19:47 ` Alan Cox
2003-03-25 18:38 ` Robert Love [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=1048617499.1486.334.camel@phantasy.awol.org \
--to=rml@tech9.net \
--cc=Robert.L.Harris@rdlg.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®