From: Dave Jones <davej@codemonkey.org.uk>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Compiling options?
Date: Tue, 25 Mar 2003 18:16:05 +0000 [thread overview]
Message-ID: <20030325181558.GA8068@suse.de> (raw)
In-Reply-To: <20030325180334.GH15678@rdlg.net>
On Tue, Mar 25, 2003 at 01:03:34PM -0500, Robert L. Harris wrote:
> Is there anything good written up on if this is the best way for our 4
> person admin team to keep managing this or should the boxes be custom
> tuned for specific groups of machines within reason? "What does it buy
> us" is one of the big questions as swapping out that many kernels and
> testing 5-8 different varriants is a big buyin on time.
Depends largely on the workload. Compiling a kernel targetted at
Athlon/Duron will factor in the 3dnow memory copying code which speeds
up bulk copies quite a lot. If your workload doesn't involve that much
memory copying, you'll likely not notice that much of a difference
though.
Dave
next prev parent reply other threads:[~2003-03-25 18:05 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 [this message]
2003-03-25 19:47 ` Alan Cox
2003-03-25 18:38 ` Robert Love
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=20030325181558.GA8068@suse.de \
--to=davej@codemonkey.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®