From: tytso@mit.edu
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: Toshiyuki Okajima <toshi.okajima@jp.fujitsu.com>,
Jan Kara <jack@suse.cz>,
akpm@linux-foundation.org, adilger@sun.com,
linux-ext4@vger.kernel.org
Subject: Re: [RFC] do you want jbd2 interface of ext3?
Date: Wed, 17 Feb 2010 14:16:29 -0500 [thread overview]
Message-ID: <20100217191629.GE5337@thunk.org> (raw)
In-Reply-To: <87f94c371002171009i2a8ffe2aib43b82c1cf65104@mail.gmail.com>
On Wed, Feb 17, 2010 at 01:09:30PM -0500, Greg Freemyer wrote:
>
> Having little knowledge on my part, it sounds like it is time to open
> up jdb3 for leading edge development and turn jdb2 into the new stable
> platform and move jdb into legacy status.
There is no "leading edge" development currently planned (nor has
there been any for at least six months or so) for the journaling
block layer.
> If it really does only have one user at this time jdb is basically
> just legacy at this point anyway.
The one user is "ext3", and for a long time jbd has only been used by
ext3. It's only recently that ocfs/ocfs2 started using jbd, and then
more recently they switch over to using jbd2.
I think people are fundamentally confused about the nature of jbd
versus ext3; jbd is a very fundamental part of ext3. Heck, jbd was
originally written *for* ext3. If jbd is "legacy", why not call ext3
"legacy"? And what the heck does "legacy" mean, anyway? If it means,
bug fixes only, that's the state of ext3 and jbd for the most part
anyway.
Yes, there have been a bunch of quota-related ext3 changes, but
they've been pretty much all been bug fixes, mainly because more
people are caring about quota now that people are much more seriously
thinking about using quota with as part of their virtualization
solution. These bugs have been around in quota for a long time, but
since time sharing is so last century, for long time it wasn't getting
much attention.
- Ted
next prev parent reply other threads:[~2010-02-17 19:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 7:41 [RFC] do you want jbd2 interface of ext3? Toshiyuki Okajima
2010-02-16 14:31 ` tytso
2010-02-16 18:54 ` Jan Kara
2010-02-17 8:36 ` Toshiyuki Okajima
2010-02-17 16:49 ` tytso
2010-02-17 18:09 ` Greg Freemyer
2010-02-17 19:16 ` tytso [this message]
2010-02-22 5:44 ` Toshiyuki Okajima
2010-02-22 13:55 ` Theodore Tso
2010-02-22 18:02 ` Jan Kara
2010-02-22 18:57 ` Dmitry Monakhov
2010-02-26 7:25 ` Toshiyuki Okajima
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=20100217191629.GE5337@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=greg.freemyer@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=toshi.okajima@jp.fujitsu.com \
/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.