From: Andrea Arcangeli <andrea@suse.de>
To: Michael Rothwell <rothwell@holly-springs.nc.us>
Cc: Josue.Amaro@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: Advanced Linux Kernel/Enterprise Linux Kernel
Date: Tue, 14 Nov 2000 18:06:02 +0100 [thread overview]
Message-ID: <20001114180602.A777@athlon.random> (raw)
In-Reply-To: <200011141459.IAA413471@tomcat.admin.navo.hpc.mil> <3A117311.8DC02909@holly-springs.nc.us>
In-Reply-To: <3A117311.8DC02909@holly-springs.nc.us>; from rothwell@holly-springs.nc.us on Tue, Nov 14, 2000 at 12:14:57PM -0500
On Tue, Nov 14, 2000 at 12:14:57PM -0500, Michael Rothwell wrote:
> Ext2 + bdflush + kupdated? Not likely. To quote the Be Filesystems
> book, Ext2 throws safety to the wind to achieve speed. This also ties
What safety problems bdflush/kupdated have? (if something they lacks in
performance since they works on a global dirty list while it should be per
queue dirty list to take the I/O pipeline full on all disks)
> [..] And the ability to grow filesystems online, [..]
This is provided in linux for ages by LVM+reiserfs also in 2.2.x.
Any filesystem with inode map and not dependent on disk offsets to find
stuff (exept the superblock of course) can do the grow almost trivially
and online, the shrink is some more complicated instead.
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-14 17:37 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-14 14:59 Advanced Linux Kernel/Enterprise Linux Kernel Jesse Pollard
2000-11-14 15:47 ` David Weinehall
2000-11-14 17:14 ` Michael Rothwell
2000-11-14 16:20 ` Mike Dresser
2000-11-14 17:27 ` Michael Rothwell
2000-11-14 17:32 ` Michael Rothwell
2000-11-14 16:25 ` Richard B. Johnson
2000-11-14 17:29 ` Michael Rothwell
2000-11-14 16:38 ` Mark Hahn
2000-11-14 19:23 ` spam
2000-11-14 16:41 ` Richard B. Johnson
2000-11-14 17:06 ` Michael Meissner
2000-11-14 17:59 ` Richard B. Johnson
2000-11-14 17:51 ` Buddha Buck
2000-11-14 18:10 ` Michael Rothwell
2000-11-14 18:00 ` Richard B. Johnson
2000-11-15 0:31 ` Gerhard Mack
2000-11-14 20:08 ` Alexander Viro
2000-11-14 16:57 ` David Relson
2000-11-14 18:17 ` Rik van Riel
2000-11-14 19:15 ` spam
2000-11-14 16:53 ` David Relson
2000-11-14 17:06 ` Andrea Arcangeli [this message]
2000-11-14 17:55 ` Andreas Dilger
2000-11-14 18:35 ` Christoph Hellwig
2000-11-14 23:06 ` Werner Almesberger
2000-11-15 4:25 ` Albert D. Cahalan
2000-11-17 22:10 ` Daniel Phillips
2000-11-18 0:58 ` Eric W. Biederman
2000-11-18 20:13 ` Daniel Phillips
2000-11-18 16:40 ` Pavel Machek
2000-11-19 20:37 ` Daniel Phillips
2000-11-20 13:34 ` Pavel Machek
2000-11-14 17:34 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2000-11-17 5:28 Bernd Eckenfels
2000-11-15 4:19 Marty Fouts
2000-11-14 18:20 Marty Fouts
2000-11-14 18:18 Marty Fouts
2000-11-14 18:10 Marty Fouts
2000-11-14 19:43 ` Steve VanDevender
2000-11-15 1:13 ` Leo Mauro
2000-11-14 18:06 Marty Fouts
2000-11-14 18:03 Marty Fouts
2000-11-08 20:31 [ANNOUNCE] Generalised Kernel Hooks Interface (GKHI) richardj_moore
2000-11-13 21:56 ` Advanced Linux Kernel/Enterprise Linux Kernel Josue Emmanuel Amaro
2000-11-14 7:49 ` Lars Marowsky-Bree
2000-11-14 18:33 ` lamont
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=20001114180602.A777@athlon.random \
--to=andrea@suse.de \
--cc=Josue.Amaro@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rothwell@holly-springs.nc.us \
/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