From: "Renato S. Yamane" <renatoyamane@mandic.com.br>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Servers comparison with Windows 2003 servers for Gaming
Date: Fri, 15 Jun 2007 11:35:22 -0300 [thread overview]
Message-ID: <4672A3AA.6010705@mandic.com.br> (raw)
In-Reply-To: <20070615152313.3638b4d5@the-village.bc.nu>
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
Alan Cox wrote:
> On Fri, 15 Jun 2007 19:42:50 +0530
>> How much better performance i will get?
>
> How long is a piece of string. Given you don't give any hardware info,
> any info on the applications run or on the network and capacity expected
> its a bit hard to guess really.
Detail: I think that is a good idea if hard-users (as kernel developers)
had a local to host yours .config file, specifying hadware.
E.g. I have a laptop Toshiba M45-S355 (with ReiserFS) and don't have
experience to choose what I can remove from kernel (or compile as
module/built-in).
So, is a great idea use pre-config file to compile a new kernel with
best options.
My .config file (2.6.21.1) and lspci is attached.
Best regards,
Renato S. Yamane
[-- Attachment #2: lspci.txt --]
[-- Type: plain/text, Size: 2122 bytes --]
[-- Attachment #3: config_2.6.21.1.txt --]
[-- Type: plain/text, Size: 59927 bytes --]
next prev parent reply other threads:[~2007-06-15 14:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 14:12 Linux Servers comparison with Windows 2003 servers for Gaming Nobin Mathew
2007-06-15 14:23 ` Alan Cox
2007-06-15 14:35 ` Renato S. Yamane [this message]
[not found] ` <200706151753.14721.mihai.dontu@gmail.com>
2007-06-15 15:47 ` Renato S. Yamane
2007-06-15 16:27 ` Jan Engelhardt
2007-06-15 16:55 ` Adrian Bunk
2007-06-15 16:28 ` Jan Engelhardt
2007-06-16 9:02 ` Willy Tarreau
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=4672A3AA.6010705@mandic.com.br \
--to=renatoyamane@mandic.com.br \
--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;
as well as URLs for NNTP newsgroup(s).