From: Tim Moore <timothymoore@bigfoot.com>
To: J Sloan <jjs@lexus.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Which kernel (Linus or ac)?
Date: Thu, 11 Oct 2001 11:56:22 -0700 [thread overview]
Message-ID: <3BC5EB56.21B4EF88@bigfoot.com> (raw)
In-Reply-To: <XFMail.20011011094548.jkp@riker.nailed.org> <3BC5E152.3D81631@bigfoot.com> <3BC5E3AF.588D0A55@lexus.com>
J Sloan wrote:
>
> Tim Moore wrote:
>
> > Any special reason to use 2.4?
>
> er... scalability, performance, features?
Observations based on Roswell 2 and identical Abit BP6's: faster disk
I/O and kernel builds (same options), smoother X11 performance (SVGA),
higher LAN network I/O (switched LNE100TX) under heavy loads, and, none
of the recent latency or VM issues. As for features, I don't need any
new feature specific to 2.4.
> > I only use 2.2.19p8 and 2.2.20p10 where
> > stability is important.
>
> experimental pre-releases? interesting...
I see your point but everything since 2.2.19p2 been stable for my NFS
and app server testing needs as well as primary desktop machine.
rgds,
tim.
--
next prev parent reply other threads:[~2001-10-11 18:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 14:45 Which kernel (Linus or ac)? jkp
2001-10-11 17:42 ` Robert Love
2001-10-11 17:52 ` Tim Connors
2001-10-11 18:11 ` Tim Moore
2001-10-12 2:01 ` Horst von Brand
[not found] ` <001901c152ca$0b42c080$0600000a@petersohn.net>
2001-10-12 18:32 ` Tim Moore
2001-10-11 18:13 ` Tim Moore
2001-10-11 18:23 ` J Sloan
2001-10-11 18:56 ` Tim Moore [this message]
2001-10-11 19:59 ` [OT] " J Sloan
2001-10-12 4:42 ` T. A.
2001-10-12 6:07 ` J Sloan
2001-10-12 9:14 ` T. A.
2001-10-12 9:59 ` Luigi Genoni
2001-10-12 17:35 ` J Sloan
2001-10-12 22:59 ` J . A . Magallon
2001-10-11 23:50 ` Oden Eriksson
2001-10-11 23:56 ` Arnaldo Carvalho de Melo
2001-10-12 0:09 ` J Sloan
2001-10-12 4:37 ` T. A.
2001-10-12 6:56 ` Ville Herva
2001-10-12 9:25 ` T. A.
2001-10-12 10:02 ` Ville Herva
2001-10-12 11:35 ` Andrea Arcangeli
2001-10-11 19:43 ` M. R. Brown
2001-10-11 22:05 ` Luigi Genoni
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=3BC5EB56.21B4EF88@bigfoot.com \
--to=timothymoore@bigfoot.com \
--cc=jjs@lexus.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.