From: Hans Reiser <reiser@namesys.com>
To: Xuan Baldauf <xuan--reiserfs@baldauf.org>
Cc: Nikita Danilov <Nikita@namesys.com>,
Tobias Oberstein <Tobias.Oberstein@gmx.de>,
Reiserfs mail-list <Reiserfs-List@namesys.com>
Subject: Re: v4 transaction design
Date: Wed, 11 Sep 2002 15:16:00 +0400 [thread overview]
Message-ID: <3D7F25F0.6080302@namesys.com> (raw)
In-Reply-To: 3D7F21E8.B7149634@baldauf.org
Xuan Baldauf wrote:
>Nikita Danilov wrote:
>
>
>
>>
>>Because we don't currently support isolation, isolation levels are not
>>exactly meaningful. But yes, one thread T1 can read data modified by
>>another thread T2 that hasn't yet committed, but at that moment "atom"
>>associated with T1 will "fuse" with atom of T2, so that they will either
>>commit of fail -both-.
>>
You should mention that we will support isolation, but we won't work on
that until after Halloween.
>>
>>
>
>So this is an implicit join of transactions. How do you ensure that livelocks do
>not happen, i.e. that T1 fails due to T2, and T2 also fails because it joined T1,
>and that thus a retry would make T1 with T2 fail again...?
>
We don't. Think of what we are doing as taking the traditional
journaling filesystem approach of not allowing rollback except in
response to crashes, and only allowing trusted plugins to use
transactions. Then understand that we will add isolation and a user API
later after the code we have is debugged.
Hans
prev parent reply other threads:[~2002-09-11 11:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-08 23:31 v4 transaction design Tobias Oberstein
2002-09-09 11:08 ` Hans Reiser
2002-09-09 11:25 ` Nikita Danilov
2002-09-11 10:58 ` Xuan Baldauf
2002-09-11 11:10 ` Nikita Danilov
2002-09-11 11:16 ` Hans Reiser [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=3D7F25F0.6080302@namesys.com \
--to=reiser@namesys.com \
--cc=Nikita@namesys.com \
--cc=Reiserfs-List@namesys.com \
--cc=Tobias.Oberstein@gmx.de \
--cc=xuan--reiserfs@baldauf.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.