From: Jeff Garzik <jeff@garzik.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andrew Morton <akpm@osdl.org>,
cmm@us.ibm.com, linux-kernel@vger.kernel.org,
ext2-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/9] sector_t format string
Date: Thu, 10 Aug 2006 09:14:57 -0400 [thread overview]
Message-ID: <44DB3151.8050904@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0608101459260.6761@scrub.home>
Roman Zippel wrote:
> On Thu, 10 Aug 2006, Jeff Garzik wrote:
>>>> Or you could just not bother, and leave everything as u64.
>>> Why?
>> To eliminate needless complexity and keep things simple and obvious?
>
> Considering the amount of complexity we add for the high end, why is it
> suddenly a bad thing to add even a _little_ complexity for the other end?
This is ext4 not ext3 we're talking about. The next gen Linux
filesystem should be tuned for modern machines -- 64bit, moving forward
-- while still working just fine on 32bit.
Jeff
next prev parent reply other threads:[~2006-08-10 13:15 UTC|newest]
Thread overview: 57+ 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 6:40 ` Andrew Morton
2006-08-10 11:05 ` Roman Zippel
2006-08-10 12:02 ` Jeff Garzik
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:30 ` Roman Zippel
2006-08-10 12:33 ` Jeff Garzik
2006-08-10 13:08 ` Roman Zippel
2006-08-10 13:14 ` Jeff Garzik [this message]
2006-08-10 13:27 ` Roman Zippel
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
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 16:54 ` Andrew Morton
2006-08-10 17:24 ` Roman Zippel
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 16:37 ` Roman Zippel
2006-08-10 21:59 ` [Ext2-devel] " Mingming Cao
2006-08-10 19:17 ` Joel Becker
2006-08-10 19:17 ` Joel Becker
2006-08-10 19:44 ` Alexey Dobriyan
2006-08-10 19:44 ` Alexey Dobriyan
2006-08-10 19:57 ` Andrew Morton
2006-08-10 19:57 ` Andrew Morton
2006-08-10 20:41 ` Alexey Dobriyan
2006-08-10 20:41 ` Alexey Dobriyan
2006-08-10 20:17 ` Jeff Mahoney
2006-08-10 20:17 ` Jeff Mahoney
2006-08-11 5:57 ` Jan Engelhardt
2006-08-11 5:57 ` Jan Engelhardt
2006-08-11 8:31 ` Bernd Petrovitsch
2006-08-11 8:31 ` Bernd Petrovitsch
2006-08-11 9:07 ` Jan Engelhardt
2006-08-11 9:07 ` Jan Engelhardt
2006-08-11 14:48 ` Jeff Mahoney
2006-08-11 14:48 ` Jeff Mahoney
2006-08-11 0:59 ` Mingming Cao
2006-08-11 2:11 ` [Ext2-devel] " Eric Sandeen
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=44DB3151.8050904@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=cmm@us.ibm.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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.