From: Roman Zippel <zippel@linux-m68k.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Jeff Garzik <jeff@garzik.org>, Andrew Morton <akpm@osdl.org>,
linux-fsdevel@vger.kernel.org, ext2-devel@lists.sourceforge.net,
cmm@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [Ext2-devel] [PATCH 2/9] sector_t format string
Date: Thu, 10 Aug 2006 16:19:54 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0608101612390.6761@scrub.home> (raw)
In-Reply-To: <44DB3CED.7080802@sandeen.net>
Hi,
On Thu, 10 Aug 2006, Eric Sandeen wrote:
> ext4 is being developed primarily to address scaling issues at the high end of
> the storage spectrum. If you're concerned about carrying 64-bit containers,
> just use ext3, and be happy with your 32-bit, < 16TB filesystems, I'd say.
The problem being that it doesn't _exclusively_ address scaling issues,
some new features may well be interesting to non high end users as well.
If it's supposed to be a high end only fs, then please don't call ext4,
otherwise it would mislead users about what it doesn't is - a general
purpose fs.
bye, Roman
next prev parent reply other threads:[~2006-08-10 14:20 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 1:20 [PATCH 2/9] sector_t format string Mingming Cao
2006-08-10 6:40 ` Andrew Morton
2006-08-10 11:05 ` Roman Zippel
2006-08-10 12:02 ` Jeff Garzik
2006-08-10 12:24 ` Roman Zippel
2006-08-10 12:25 ` Jeff Garzik
2006-08-10 12:30 ` Roman Zippel
2006-08-10 12:33 ` Jeff Garzik
2006-08-10 13:08 ` Roman Zippel
2006-08-10 13:14 ` Jeff Garzik
2006-08-10 13:27 ` Roman Zippel
2006-08-10 13:30 ` Jeff Garzik
2006-08-10 13:52 ` Roman Zippel
2006-08-10 14:04 ` [Ext2-devel] " Eric Sandeen
2006-08-10 14:19 ` Roman Zippel [this message]
2006-08-10 14:21 ` Jeff Garzik
2006-08-10 14:35 ` Roman Zippel
2006-08-10 14:06 ` Jeff Garzik
2006-08-10 14:24 ` Roman Zippel
2006-08-10 14:26 ` Jeff Garzik
2006-08-10 14:41 ` Roman Zippel
2006-08-10 16:24 ` John Stoffel
2006-08-10 16:43 ` Roman Zippel
2006-08-10 16:54 ` Andrew Morton
2006-08-10 17:24 ` Roman Zippel
2006-08-10 15:31 ` [Ext2-devel] " Theodore Tso
2006-08-10 16:37 ` Roman Zippel
2006-08-10 21:59 ` [Ext2-devel] " Mingming Cao
2006-08-10 19:17 ` Joel Becker
2006-08-10 19:44 ` Alexey Dobriyan
2006-08-10 19:57 ` Andrew Morton
2006-08-10 20:41 ` Alexey Dobriyan
2006-08-10 20:17 ` Jeff Mahoney
2006-08-11 5:57 ` Jan Engelhardt
2006-08-11 8:31 ` Bernd Petrovitsch
2006-08-11 9:07 ` Jan Engelhardt
2006-08-11 14:48 ` Jeff Mahoney
2006-08-11 0:59 ` Mingming Cao
2006-08-11 2:11 ` Eric Sandeen
2006-08-11 22:06 ` Mingming Cao
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=Pine.LNX.4.64.0608101612390.6761@scrub.home \
--to=zippel@linux-m68k.org \
--cc=akpm@osdl.org \
--cc=cmm@us.ibm.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=jeff@garzik.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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).