From: Olaf van der Spek <olafvdspek@gmail.com>
To: Christian Stroetmann <stroetmann@ontolinux.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
"Ted Ts'o" <tytso@mit.edu>, Ric Wheeler <rwheeler@redhat.com>,
Amir Goldstein <amir73il@gmail.com>
Subject: Re: Atomic file data replace API
Date: Wed, 29 Dec 2010 18:12:19 +0100 [thread overview]
Message-ID: <AANLkTi=UCqBzFuUnK5CFCo=YG4q0G51GKRr2BCeeZahv@mail.gmail.com> (raw)
In-Reply-To: <4D1B6217.6020300@ontolinux.com>
On Wed, Dec 29, 2010 at 5:30 PM, Christian Stroetmann
<stroetmann@ontolinux.com> wrote:
>> I'm talking about the code for temp file, fsync, rename. Not about
>> O_ATOMIC code.
>
> Maybe you have not understood the hints: It doesn't matter anymore about
> what you are talking unless you present code.
What code?
>>>> Each app makes it's own decision about what API to use. Supporting
>>>> atomic stuff doesn't change the behaviour of existing apps.
>>>
>>> Wrong, we are talking here in the first place about general atomic FS
>>> operations. And to guarantee atomicity you have to change general FS
>>> functions in such a way that in the end all other applications are
>>> affected,
>>
>> Why's that?
>
> read the paragraph as a whole
I have. Still wondering why.
next prev parent reply other threads:[~2010-12-29 17:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 11:51 Atomic file data replace API Olaf van der Spek
2010-12-27 13:20 ` Amir Goldstein
2010-12-27 15:53 ` Olaf van der Spek
2010-12-27 17:20 ` Amir Goldstein
2010-12-27 18:34 ` Olaf van der Spek
2010-12-28 2:59 ` Ted Ts'o
2010-12-28 17:27 ` Olaf van der Spek
2010-12-28 19:06 ` Ric Wheeler
2010-12-28 22:25 ` Olaf van der Spek
2010-12-28 22:36 ` Ric Wheeler
2010-12-28 22:58 ` Olaf van der Spek
2010-12-29 9:20 ` Amir Goldstein
2010-12-29 12:42 ` Olaf van der Spek
2010-12-29 15:30 ` Christian Stroetmann
2010-12-29 15:35 ` Olaf van der Spek
2010-12-29 16:30 ` Christian Stroetmann
2010-12-29 17:12 ` Olaf van der Spek [this message]
2010-12-29 17:15 ` Greg Freemyer
2010-12-29 19:30 ` Christian Stroetmann
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='AANLkTi=UCqBzFuUnK5CFCo=YG4q0G51GKRr2BCeeZahv@mail.gmail.com' \
--to=olafvdspek@gmail.com \
--cc=amir73il@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rwheeler@redhat.com \
--cc=stroetmann@ontolinux.com \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).