All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Geoff Oakham <g@mbl.ca>
Cc: Yury Umanets <umka@namesys.com>,
	reiserfs-list@namesys.com, demidov <demidov@thebsh.namesys.com>
Subject: Re: libaal documentation: fact or fiction?
Date: Thu, 09 Oct 2003 14:19:02 +0400	[thread overview]
Message-ID: <3F853616.8010808@namesys.com> (raw)
In-Reply-To: <20031008163202.GA2185@mbl.ca>

Geoff Oakham wrote:

>Hi Yury,
>
>Thanks for getting back to me!
>
>On Wed, Oct 08, 2003 at 10:52:20AM +0400, Yury Umanets wrote:
>  
>
>>Libaal has been developed as a try of standard interface between 
>>corresponding FS userspace library (currently libreiser4) and 
>>application that wants to use that library (currently reiser4progs).
>>    
>>
>
>Is this library the userland interface applications use to write to
>files in atomic operations?
>
No, sys_reiser4 is.  sys_reiser4 is currently in a quite raw state.  You 
might want to contact us again in 3 months.

We do not support isolation in transactions yet.  We only support 
atomicity.  Atomicity is easier to implement without complications 
regarding performance and deadlock than isolation.

>
>  
>
>>BTW, why do you interested in documenting it?
>>    
>>
>
>A number of reasons: I'm interested in ReiserFs4 and I want to start
>playing with it.  As I understand it, Reiserfs4 will offer data
>journalling and plugin support.. both things I'd like to play with.
>Since neither seems to have been documented yet, I thought I'd start by
>attempting that.
>
>I'm also intersted because data-journalling has the potential to become
>a standard interface for Linux filesystems.. and as an outsider I was
>hoping I would be able to offer suggestions on how to clean up that API
>and speed up its acceptance.  Futhermore, I want to see if it's possible
>to implement the equivalent functionality (at least from a programmer's
>perspective) on a traditional UNIX filesystem using old-fasioned
>file-locking.
>
>Cheers,
>
>Geoff
>
>  
>


-- 
Hans



  parent reply	other threads:[~2003-10-09 10:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 17:22 libaal documentation: fact or fiction? Geoff Oakham
2003-10-08  6:52 ` Yury Umanets
2003-10-08 16:32   ` Geoff Oakham
2003-10-08 18:12     ` Yury Umanets
2003-10-08 19:01       ` Geoff Oakham
2003-10-08 19:56         ` Yury Umanets
2003-10-08 20:46           ` Geoff Oakham
2003-10-09  9:20             ` Yury Umanets
2003-10-09 10:19     ` Hans Reiser [this message]
2003-10-09 12:51       ` Geoff Oakham

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=3F853616.8010808@namesys.com \
    --to=reiser@namesys.com \
    --cc=demidov@thebsh.namesys.com \
    --cc=g@mbl.ca \
    --cc=reiserfs-list@namesys.com \
    --cc=umka@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.