[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fuse-devel
Subject:    Re: [fuse-devel] filesystem guarantees for multi-threaded access
From:       Han-Wen Nienhuys <hanwenn () gmail ! com>
Date:       2011-10-02 19:00:43
Message-ID: CAOw_e7YO_pkpqyFg+-QRHKnad3E_CA=is4NjFoRVsRB3dUBbFA () mail ! gmail ! com
[Download RAW message or body]

On Sun, Oct 2, 2011 at 3:28 PM, Stefan Westerfeld <stefan@space.twc.de> wrote:

> I wonder what guarantees a filesystem has to give when more than one thread is
> involved. For instance, if thread 1 and thread 2 access the same file, and
>
>  thread 1 - writes ("thread 1") to file foo
>  thread 2 - writes ("thread 2") to file foo, a tiny bit later
>
> does a filesystem have to guarantee that the file foo contains "thread 2" after
> this?

No, if userland wants to have guarantees about ordering, it should
issue the 2nd write after the 1st write returns, in which case the
fuse FS will not process them simultaneously.

-- 
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
fuse-devel mailing list
fuse-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fuse-devel

[prev in list] [next in list] [prev in thread] [next in thread]