From: Kuba Ober <kuba@mareimbrium.org>
To: reiserfs-list@namesys.com
Subject: Re: jbd layer + reiserfs
Date: Wed, 12 Jun 2002 18:04:13 -0400 [thread overview]
Message-ID: <200206121804.13209.kuba@mareimbrium.org> (raw)
In-Reply-To: <20020612215110.GA18661@matrix.wg>
On ¶roda 12 czerwiec 2002 05:51 pm, Dirk Mueller wrote:
> Hi,
>
> just being curious: is reiserfs anywhen going to use the jbd layer that was
> introduced with the ext3 kernel merge ?
I don't think that reiserfs journalling semantics are simple enough to be
replicated by a journalled block device... that's my guess, I'm just a user,
not a developer.
Alas... well, maybe I'm wrong. If instead of opening and closing transactions
in reiserfs journal it would be calling jfs transaction boundaries, maybe
it's the same. Does reiserfs do any more magic in its journalling than simpky
journal metadata block-writing?
If it would be able to use jbd layer, then I assume some of the journal code
could be put away (ie: dumped), at least in linux kernel tree (is there
reiserfs for other platforms at all?).
Cheers, Kuba Ober
prev parent reply other threads:[~2002-06-12 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-12 21:51 jbd layer + reiserfs Dirk Mueller
2002-06-12 22:04 ` Kuba Ober [this message]
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=200206121804.13209.kuba@mareimbrium.org \
--to=kuba@mareimbrium.org \
--cc=reiserfs-list@namesys.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.