From: John Richard Moser <nigelenki@comcast.net>
To: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Collapse ext2 and 3 please
Date: Fri, 25 Jun 2004 19:48:18 -0400 [thread overview]
Message-ID: <40DCB9C2.5000605@comcast.net> (raw)
In-Reply-To: <20040625150021.3f50350b.akpm@osdl.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andrew Morton wrote:
| Sean Neakums <sneakums@zork.net> wrote:
|
|>I seem to remember somebody, I think maybe Andrew Morton, suggesting
|>that a no-journal mode be added to ext3 so that ext2 could be removed.
|>I can't find the message in question right now, though.
|
|
| I think it could be done, mainly as a kernel-space-saving exercise. But
| the two filesystems are quite different nowadays.
|
| ext2 uses per-inode pagecache for directories, ext3 uses blockdev
| pagecache. The truncate algorithms are significantly different. Other
stuff.
|
So why isn't it feasible to keep truncate algorithms and pagecache code
separated while collapsing the rest? Same logic as i said in another reply:
if (journaled)
~ extfs_journaled_truncate();
else
~ extfs_nonjournaled_truncate();
| Much pain, little gain.
I understand this; but all work done is volunteer, so it'll only get
done if someone wants to do it :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA3LnAhDd4aOud5P8RApugAJ45XGfdVGxVSEYsk/N55S4r5Qd+BACgi1vp
cgv421B9Yxc3EX/TUv/nm+M=
=bZBQ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-06-25 23:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 23:14 Collapse ext2 and 3 please John Richard Moser
2004-06-25 9:16 ` Helge Hafting
2004-06-25 11:30 ` David van Hoose
2004-06-25 11:41 ` Christoph Hellwig
2004-06-25 11:50 ` David van Hoose
2004-06-25 12:01 ` Matthew Garrett
[not found] ` <1088165028.16286.59.camel@imp.csi.cam.ac.uk>
2004-06-25 12:05 ` David van Hoose
2004-06-25 12:13 ` Matthew Garrett
[not found] ` <1088165426.16286.67.camel@imp.csi.cam.ac.uk>
2004-06-25 12:18 ` David van Hoose
2004-06-25 13:03 ` Tigran Aivazian
2004-06-25 12:40 ` David van Hoose
2004-06-25 14:03 ` Rik van Riel
2004-06-25 12:10 ` Christoph Hellwig
2004-06-25 12:15 ` David van Hoose
2004-06-25 12:26 ` Richard B. Johnson
2004-06-25 12:48 ` Philip R. Auld
2004-06-25 12:53 ` David van Hoose
2004-06-25 13:39 ` Tigran Aivazian
2004-06-25 18:55 ` David van Hoose
2004-06-25 22:26 ` John Richard Moser
2004-06-25 12:25 ` Sean Neakums
2004-06-25 18:01 ` Timothy Miller
2004-06-25 18:04 ` Sean Neakums
2004-06-25 18:41 ` Timothy Miller
2004-06-25 20:52 ` R. J. Wysocki
2004-06-25 20:50 ` Sean Neakums
2004-06-25 21:36 ` R. J. Wysocki
2004-06-25 22:00 ` Andrew Morton
2004-06-25 23:48 ` John Richard Moser [this message]
[not found] <2aZfF-3es-5@gated-at.bofh.it>
[not found] ` <2b45V-6tl-39@gated-at.bofh.it>
2004-06-25 22:28 ` Pascal Schmidt
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=40DCB9C2.5000605@comcast.net \
--to=nigelenki@comcast.net \
--cc=akpm@osdl.org \
--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