From: Jamie Lokier <jamie@shareable.org>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: Mark Fasheh <mfasheh@suse.com>,
linux-fsdevel@vger.kernel.org, Sage Weil <sage@newdream.net>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
Andreas Dilger <adilger@sun.com>
Subject: Re: [PATCH 1/2] [RFC] vfs: 'stat light' fstatat flags
Date: Tue, 7 Apr 2009 19:16:10 +0100 [thread overview]
Message-ID: <20090407181610.GH31824@shareable.org> (raw)
In-Reply-To: <1D2105EA-A7C8-46C8-8AB9-380F9FCA7730@linuxhacker.ru>
Oleg Drokin wrote:
> >>AT_STRICT allows userspace to indicate that it wants the most up to
> >>date
> >>version of a files status, regardless of performance impact. A
> >>distributed
> >>file system which has a non-coherent inode cache would know then to
> >>send a
> >>direct query to it's server.
> >Good idea! Sort out some NFS pain.
> >If a filesystem doesn't honour AT_STRICT, can we have the function
> >return an error instead of stale values?
>
> Supposedly the existing stat() is the way to do this?
I don't understand your response. If an application wants to be sure
it has non-stale attributes, how does stat() help? Are you saying
stat() does this? (Afaik it doesn't on NFS).
-- Jamie
next prev parent reply other threads:[~2009-04-07 18:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 8:00 [PATCH 1/2] [RFC] vfs: 'stat light' fstatat flags Mark Fasheh
2009-04-07 10:23 ` Andreas Dilger
2009-04-07 14:59 ` Oleg Drokin
2009-04-07 15:18 ` Sage Weil
2009-04-07 15:29 ` Mark Fasheh
2009-04-07 17:52 ` Andreas Dilger
2009-04-07 18:13 ` Jamie Lokier
2009-04-07 23:13 ` Russell Cattelan
2009-04-07 17:42 ` Jamie Lokier
2009-04-07 17:48 ` Oleg Drokin
2009-04-07 18:16 ` Jamie Lokier [this message]
2009-04-07 18:24 ` Oleg Drokin
2009-04-07 20:37 ` Trond Myklebust
2009-04-08 18:48 ` Jamie Lokier
2009-04-09 15:13 ` 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=20090407181610.GH31824@shareable.org \
--to=jamie@shareable.org \
--cc=Trond.Myklebust@netapp.com \
--cc=adilger@sun.com \
--cc=green@linuxhacker.ru \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=sage@newdream.net \
/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).