mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Marcin Hlybin <marcin.hlybin@swmind.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Open Discussion, kernel in production environment
Date: Tue, 02 May 2006 09:01:14 +0200	[thread overview]
Message-ID: <1146553275.32045.15.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <200605012357.48623.marcin.hlybin@swmind.com>

On Mon, 2006-05-01 at 23:57 +0200, Marcin Hlybin wrote:
> Hello,
> 
> I always configure and compile a kernel throwing out all unusable options and 
> I never use modules in production environment (especially for the router). 
> But my superior has got the other opinion - he claims that distribution 
> kernel is quite good and in these days optimization has no sense because of 
> powerful hadrware. 


he's basically right; the gain you get by disabling the generic things a
distribution enabled is way down in the noise. There are some
compromises a distribution makes to keep the number of kernels they ship
down, and I suspect the worst possible case would add up to say 5%.

(on a Fedora / RHEL that would probably be a SMP system with less than
1Gb of ram)

On the plus side you get the maintenance, building and integration done
for you, including the security fixes. 

There is a third "advantage" in using a distro kernel; there is less
chance of a mistake in the sense of picking a config option that turns
out to be really bad in hindsight. 

Now that doesn't mean that I want to discourage people from building
their own kernel, far from that, but at the same time, the advantages
you get shouldn't be overstated and in a business environment it is
probably not a good use of time nowadays.


  parent reply	other threads:[~2006-05-02  7:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-01 21:57 Marcin Hlybin
2006-05-01 22:36 ` Bernd Eckenfels
2006-05-02  6:57 ` Andi Kleen
2006-05-02  7:01 ` Arjan van de Ven [this message]
2006-05-02 11:29   ` Jan Engelhardt
2006-05-03  1:06 ` David Lang
2006-05-03  2:30   ` Grant Coady
2006-05-03 16:40     ` Jan Engelhardt

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=1146553275.32045.15.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin.hlybin@swmind.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

all inboxes | Powered by JetHome®