From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andreas Dilger <adilger@clusterfs.com>, Alex Tomas <bzzz@tmi.comex.ru>
Cc: Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: [PATCH] concurrent block allocation for ext2 against 2.5.64
Date: Fri, 14 Mar 2003 10:25:48 -0800 [thread overview]
Message-ID: <120000000.1047666348@flay> (raw)
In-Reply-To: <20030313165641.H12806@schatzie.adilger.int>
> First of all, thanks for this work, Alex. It's been a long time in coming.
>
> One thing I would wonder about is whether we should be implementing this in
> ext2, or in ext3 only. One of the decisions we made in the past is that we
> shouldn't necessarily implement everything in ext2 (especially features that
> complicated the code, and are only useful on high-end systems).
>
> There was a desire to keep ext2 small and simple, and ext3 would get the
> fancy high-end features that make sense if you have a large filesystem
> that you would likely be using in conjunction with ext3 anyways.
Errrm ... if you want to start advocating that sort of thing, I suggest
you make ext3 usable on high end systems first. At the moment, that makes
no sense whatsoever. Ext3 still doesn't scale to big systems.
M.
next prev parent reply other threads:[~2003-03-14 18:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 8:55 [PATCH] concurrent block allocation for ext2 against 2.5.64 Alex Tomas
2003-03-13 9:58 ` Andrew Morton
2003-03-13 19:17 ` Alex Tomas
2003-03-13 22:25 ` Andrew Morton
2003-03-13 23:03 ` Andreas Dilger
2003-03-13 23:10 ` Andrew Morton
2003-03-13 23:03 ` Alex Tomas
2003-03-13 23:25 ` Andrew Morton
2003-03-13 23:56 ` Andreas Dilger
2003-03-14 7:20 ` Alex Tomas
2003-03-14 20:59 ` Andreas Dilger
2003-03-14 21:14 ` Alex Tomas
2003-03-15 4:37 ` William Lee Irwin III
2003-03-15 4:54 ` Andrew Morton
2003-03-15 5:30 ` William Lee Irwin III
2003-03-15 5:43 ` Martin J. Bligh
2003-03-15 5:50 ` William Lee Irwin III
2003-03-15 5:49 ` William Lee Irwin III
2003-03-15 6:20 ` William Lee Irwin III
2003-03-15 6:44 ` Andrew Morton
2003-03-15 7:05 ` William Lee Irwin III
2003-03-15 8:24 ` William Lee Irwin III
2003-03-15 9:47 ` William Lee Irwin III
2003-03-15 11:58 ` William Lee Irwin III
2003-03-15 12:08 ` Andrew Morton
2003-03-15 12:25 ` William Lee Irwin III
2003-03-15 8:16 ` [Ext2-devel] " Alex Tomas
2003-03-15 8:29 ` William Lee Irwin III
2003-03-15 8:32 ` Alex Tomas
2003-03-15 9:23 ` William Lee Irwin III
2003-03-14 18:25 ` Martin J. Bligh [this message]
2003-03-14 19:30 ` Daniel Phillips
2003-03-14 19:55 ` Andrew Morton
2003-03-13 17:39 ` [Ext2-devel] " Andreas Dilger
2003-03-13 18:43 ` Alex Tomas
2003-03-13 19:09 ` Matthew Wilcox
2003-03-13 19:39 ` Andrew Morton
2003-03-13 19:23 ` Theodore Ts'o
2003-03-13 19:44 ` Andreas Dilger
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=120000000.1047666348@flay \
--to=mbligh@aracnet.com \
--cc=adilger@clusterfs.com \
--cc=akpm@digeo.com \
--cc=bzzz@tmi.comex.ru \
--cc=ext2-devel@lists.sourceforge.net \
--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