From: Eric Valette <eric.valette@free.fr>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: 2.4.22 timeline was RE: 2.4.21-rc7 ACPI broken
Date: Thu, 12 Jun 2003 13:47:48 +0200 [thread overview]
Message-ID: <3EE86864.5070207@free.fr> (raw)
In-Reply-To: <20030611211506.GD16164@fs.tum.de>
Adrian Bunk wrote:
> On Wed, Jun 11, 2003 at 01:40:54AM +0200, Eric Valette wrote:
>
>>...
>>I would personnally suggest that you classify the things using the
>>following filter :
>> a) Server (SMP, SCSI, RAID, journaling filesystems, ...),
>> b) laptop (ACPI, CPUFREQ, Software suspend, IDE power save,...),
>> c) desktop (File system efficiency, new hardware support,...),
>> d) all systems
>>...
>
>
> Why are journaling filesystems only for servers?
> Is file system efficiency not relevant on servers?
I was just making suggestions after a 30s thinking. Side comments,
readding this mailling list, I had the impression that journaling and
filesystem performance do not seem to mix well. Also on server, you have
probably extra backup hardware and means (e.g RAID, DAT, DLT, ...)
> The important sections are more likely (ordered by priority):
> - bug fixes (e.g. aic7xxx)
> - support for additional hardware (e.g. ACPI update)
> - new features (e.g. XFS)
Personnaly, I dislike this approach as it as resulted in 2.4 being non
usable for servers (SMP deadlocks, IO stalls, unresponsiveness for
several seconds, ...) and laptop (ACPI)...
> The important thing is that this is inside a stable kernel series and an
> update that makes things better for 100 people but makes things worse
> for one person is IMHO bad since it's a regression for one person.
If 2.4 kernel is not usable without patching, It is far worse for me...
--
__
/ ` Eric Valette
/-- __ o _. 6 rue Paul Le Flem
(___, / (_(_(__ 35740 Pace
Tel: +33 (0)2 99 85 26 76 Fax: +33 (0)2 99 85 26 76
E-mail: eric.valette@free.fr
next prev parent reply other threads:[~2003-06-12 11:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 23:40 2.4.22 timeline was RE: 2.4.21-rc7 ACPI broken Eric Valette
2003-06-11 21:15 ` Adrian Bunk
2003-06-12 11:47 ` Eric Valette [this message]
2003-06-12 14:05 ` Stephan von Krawczynski
2003-06-12 16:32 ` Eric Valette
2003-06-17 23:25 ` Marcelo Tosatti
2003-06-17 23:58 ` J.A. Magallon
2003-06-18 20:27 ` Marcelo Tosatti
2003-06-18 5:15 ` Anders Karlsson
2003-06-18 16:55 ` Bill Nottingham
2003-06-18 9:04 ` Eric Valette
-- strict thread matches above, loose matches on Subject: below --
2003-06-09 23:27 Grover, Andrew
2003-06-09 22:38 Margit Schubert-While
2003-06-10 0:08 ` Marcelo Tosatti
2003-06-09 21:47 Margit Schubert-While
2003-06-09 21:21 Grover, Andrew
2003-06-09 21:24 ` Grzegorz Jaskiewicz
2003-06-09 22:03 ` Marcelo Tosatti
2003-06-10 0:44 ` Alan Cox
2003-06-10 11:05 ` Torben Mathiasen
2003-06-10 15:14 ` Stephan von Krawczynski
2003-06-09 21:07 Margit Schubert-While
2003-06-04 20:49 Grover, Andrew
2003-06-09 20:32 ` 2.4.22 timeline was " Marcelo Tosatti
2003-06-10 0:47 ` Alan Cox
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=3EE86864.5070207@free.fr \
--to=eric.valette@free.fr \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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.