lkml.org 
[lkml]   [2005]   [Apr]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: filesystem transactions API
    Jamie Lokier wrote:
    > Artem B. Bityuckiy wrote:
    >
    > No. A transaction means that _all_ processes will see the whole
    > transaction or not.
    >
    > It does _not_ mean that only a subset of programs, which happen to
    > link with a particular user-space library, will see it or not.
    >
    > For example, you can use transactions for distro package management: a
    > whole update of a package would be a single transaction, so that at no
    > time does any program see an inconsistent set of files. See why
    > _every_ process in the system must have the same view?
    >
    > [ If you meant that you can implement it with a user-space library
    > that every process in the system links to, that's true. But it would
    > rather misses the point of having filesystems in the kernel at all :) ]
    >
    Hmm, so the whole point to implement transactions in the kernel space is
    to do the transactions in a way that nobody can see any intermediate
    inconsistent state ?


    --
    Best regards, Artem B. Bityuckiy
    Oktet Labs (St. Petersburg), Software Engineer.
    +78124286709 (office) +79112449030 (mobile)
    E-mail: dedekind@oktetlabs.ru, web: http://www.oktetlabs.ru
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-04-26 16:49    [W:6.288 / U:0.660 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site