Messages in this thread | | | Date | Wed, 27 Apr 2005 11:14:03 +0200 | From | Jan Hudec <> | Subject | Re: filesystem transactions API |
| |
On Tue, Apr 26, 2005 at 20:01:45 +0400, Artem B. Bityuckiy wrote: > Jamie Lokier wrote: > >No. Why would you block? You can have transactions without blocking > >other processes. > > > >When updating, say, the core-utils package (which contains cat), > >there's no reason why a program which executes "cat" should have to > >block during the update. It can simply execute the old one until the > >new one is committed at the end of the update. > > > >It's analogous to RCU for protecting kernel data structures without > >blocking readers. > > > Hmm, can't we implement a user-space locking system which admits of > readers during transactions? I gues we can.
The problem with implementing in userland, as was already said in the thread, is, that if some process does not use the library, it can completely mess it up. It is only safe in kernel.
------------------------------------------------------------------------------- Jan 'Bulb' Hudec <bulb@ucw.cz> [unhandled content-type:application/pgp-signature] | |