mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: be-news06@lina.inka.de (Bernd Eckenfels)
To: linux-kernel@vger.kernel.org
Subject: Re: Open Discussion, kernel in production environment
Date: Tue, 02 May 2006 00:36:03 +0200	[thread overview]
Message-ID: <E1Fagzr-0003cG-00@calista.inka.de> (raw)
In-Reply-To: <200605012357.48623.marcin.hlybin@swmind.com>

Marcin Hlybin <marcin.hlybin@swmind.com> wrote:
> 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. 

I think it is most often wasted time to optimize your kernels that way,
especially if you consider the ongoing work you have to put into maintenance
of it.

So unlike you plan to roll out hundreds of systems with the same image
(containing a hand made kernel) I would not suggest to do it.

Of course I am not talking about embedded systems here. For larger Servers
(NUMA, Terrayte Ram stuff like that) I also would think you might want to go
with the Vendor kernel, for better support.

For production use with things like Oracle or SAP, I would suggest to not
use uncertified kernels anyway.

Gruss
Bernd

  reply	other threads:[~2006-05-01 22:36 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 [this message]
2006-05-02  6:57 ` Andi Kleen
2006-05-02  7:01 ` Arjan van de Ven
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=E1Fagzr-0003cG-00@calista.inka.de \
    --to=be-news06@lina.inka.de \
    --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®