public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Michael D. Setzer II" <mikes@kuentos.guam.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel options for cd project with processor family
Date: Tue, 2 Aug 2005 12:56:12 -0400	[thread overview]
Message-ID: <20050802165612.GB18410@redhat.com> (raw)
In-Reply-To: <42EFDC63.31465.58ED66@mikes.kuentos.guam.net>

On Tue, Aug 02, 2005 at 08:49:39PM +1000, Michael D. Setzer II wrote:
 > I'm working on the ghost for linux project, which uses various 
 > kernels. The older version 0.14 version had two kernels that support 
 > some configurations. I've added a number of additional builds 
 > adding extra features, but left earlier version in case the later 
 > additions didn't work with hardware. The bzImage6 is the latest and 
 > it works with most hardware, but I found it didn't work on a K6, since 
 > it was build with the Pentium Pro Family. I was able to build one with 
 > the K6 family, and it worked. I had used one of the original kernels 
 > with a K6 before, but this one had a network card that wasn't 
 > supported by it. 
 > 
 > I've built a test set of kernels with the same configuration as the 
 > bzImage6, but changed the Processor family. Below is a list of the 
 > build. I'm interested in which ones would make a difference. I would 
 > think that the 386 version would probable work on all hardware, but 
 > at what cost in performance for creating and restoring the disk 
 > images. G4L uses basically dd, gzip, lzop, bzop, ncftpget, and 
 > ncftpput. With all these images, the g4l iso image is 50MB. 

Your workload is going to be almost entirely IO bound, with
the only CPU intensive parts being 99% in userspace. So any
performance gains by tuning the kernel for a specific CPU are
likely to be unnoticable.  I'd go with a single image supporting
the lowest hardware you intend to support.

CPU tuned variants of gzip/bzip may be more noticable however.

		Dave


  parent reply	other threads:[~2005-08-02 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02 10:49 kernel options for cd project with processor family Michael D. Setzer II
     [not found] ` <42F02850.4352.1818D8B@mikes.kuentos.guam.net>
2005-08-02 16:39   ` Jan Engelhardt
2005-08-02 16:56 ` Dave Jones [this message]
2005-08-02 18:58 ` Jesper Juhl

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=20050802165612.GB18410@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikes@kuentos.guam.net \
    /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