From: Jamie Lokier <jamie@shareable.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] atomic create+open
Date: Thu, 6 Oct 2005 18:59:40 +0100 [thread overview]
Message-ID: <20051006175940.GA19766@mail.shareable.org> (raw)
In-Reply-To: <1128620196.16534.20.camel@lade.trondhjem.org>
Trond Myklebust wrote:
> > Earlier you said, that intents are meant to be optional, so this
> > atomicity requirement is getting further from the "intent" concept.
>
> No it is not. It is bang right in the middle of the intent concept.
>
> Intents are there in order to allow the filesystem to determine which
> operation is calling lookup so that it can optimise for that particular
> operation.
I think Miklos' point is that it's not an "optimisation" because it's
not optional. Optimisations are things where if you don't do them,
the behaviour is still correct but slower.
As far as I can tell from this discussion, the atomic lookup+create is
a non-optional requirement.
-- Jamie
next prev parent reply other threads:[~2005-10-06 17:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 14:38 [RFC] atomic create+open Miklos Szeredi
2005-10-06 16:41 ` Trond Myklebust
2005-10-06 17:02 ` Miklos Szeredi
2005-10-06 17:06 ` Miklos Szeredi
2005-10-06 17:25 ` Trond Myklebust
2005-10-06 17:30 ` Miklos Szeredi
2005-10-06 17:42 ` Trond Myklebust
2005-10-06 17:51 ` Miklos Szeredi
2005-10-06 18:00 ` Jamie Lokier
2005-10-06 18:48 ` Daniel Jacobowitz
2005-10-06 18:38 ` Trond Myklebust
2005-10-06 18:49 ` Miklos Szeredi
2005-10-06 19:17 ` Trond Myklebust
2005-10-06 20:17 ` Miklos Szeredi
2005-10-06 21:12 ` Trond Myklebust
2005-10-07 6:01 ` Miklos Szeredi
2005-10-07 13:38 ` Trond Myklebust
2005-10-07 13:59 ` Miklos Szeredi
2005-10-07 14:47 ` Trond Myklebust
2005-10-07 15:18 ` Miklos Szeredi
2005-10-07 16:01 ` Trond Myklebust
2005-10-07 17:20 ` Miklos Szeredi
2005-10-07 15:13 ` Trond Myklebust
2005-10-07 15:28 ` Miklos Szeredi
2005-10-07 16:23 ` Trond Myklebust
2005-10-07 17:27 ` Miklos Szeredi
2005-10-07 17:36 ` Trond Myklebust
[not found] ` <1129061494.11164.38.camel@lade.trondhjem.org>
[not found] ` <E1EPeM4-0000Xz-00@dorka.pomaz.szeredi.hu>
2005-10-12 13:20 ` Trond Myklebust
2005-10-12 13:52 ` Miklos Szeredi
2005-10-12 19:01 ` Trond Myklebust
2005-10-12 19:53 ` Miklos Szeredi
2005-10-12 15:20 ` Miklos Szeredi
2005-10-06 17:07 ` Trond Myklebust
2005-10-06 17:23 ` Miklos Szeredi
2005-10-06 17:36 ` Trond Myklebust
2005-10-06 17:47 ` Miklos Szeredi
2005-10-06 17:59 ` Jamie Lokier [this message]
2005-10-06 18:13 ` Miklos Szeredi
2005-10-06 18:42 ` Trond Myklebust
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=20051006175940.GA19766@mail.shareable.org \
--to=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=trond.myklebust@fys.uio.no \
/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