Re: reiser4 data journalling?

[Hans Reiser <reiser@namesys.com>]

Lars Marowsky-Bree wrote:

>On 2003-09-03T02:17:50,
>   Hans Reiser <reiser@namesys.com> said:
>
>  
>
>>No, isolation is not yet implemented and won't be unless we come up with 
>>some more funding from somewhere.  The txnmgr seems to be structured to 
>>handle isolation, but....
>>    
>>
>
>Ah, okay. Sorry, I think I had older plans in mind and hadn't checked
>how far the current roadmap matched up to them ;-)
>
>  
>
>>The new thing with reiser4 is that if you do that write of 1MB to a 
>>file, and perhaps updates to 63 other files as well, as part of an atom, 
>>it will either all survive a crash, or none of it will.  We have 
>>considered using the term "transcrash" for this.
>>    
>>
>
>So it's ACD and not ACID ;-) Sounds good. How is this weak transaction
>exported to userspace, ie how do I signal BEGIN and COMMIT/ABORT?
>
>
>
>Sincerely,
>    Lars Marowsky-Brée <lmb@suse.de>
>
>  
>
sys_reiser4 allows various operations such as assignment, and 
transactions are indicated using a delimiter.  I am still trying to 
figure out what is the best delimiter to use, it needs to be a delimiter 
pair, but what?

Perhaps t{ and }t

?

I worry that users will let a legitimate t variable name get too close 
to the {}'s.....

There is a symbol shortage unfortunately.

Probably I should use x{ and }x as a convention for new kinds of 
delimiters, and let x be t in the case of delimiting transactions.

-- 
Hans