From: Russell Cattelan <cattelan@thebarn.com>
To: Andreas Dilger <adilger@sun.com>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/2] [RFC] vfs: 'stat light' fstatat flags
Date: Tue, 07 Apr 2009 18:13:35 -0500 [thread overview]
Message-ID: <49DBDE1F.5070408@thebarn.com> (raw)
In-Reply-To: <20090407102332.GS3204@webber.adilger.int>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andreas Dilger wrote:
> On Apr 07, 2009 01:00 -0700, Mark Fasheh wrote:
>> This very, very rough patch set adds three flags to fstatat -
>> AT_NO_SIZE, AT_NO_TIMES, and AT_STRICT.
>
> It seems you and Oleg have two patches crossing in the night...
>
>> The first two flags (AT_NO_SIZE, AT_NO_TIMES) allow userspace to
>> notify the file system layer that certain stat fields are not
>> required to be accurate.
>
> The problem with "AT_NO_*" is that old applications which couldn't
> possibly know about or use a new stat field couldn't possibly know
> not to ask for it. Instead, as was proposed in the last generation
> of this thread, there should be
> AT_GET_{ATIME,MTIME,CTIME,BLOCKS,SIZE,NLINKS,...}, to return the
> flags that the application actually wants. If none of them are
> specified, then the current behaviour of "get all attributes" is
> kept.
>
I agree with implementing positive flags "I want" vs negative flags "I
don't want", any application that is going to
actually go to the effort to selectively pick which stat fields it
wants is only expecting that particular
information to be returned. The use of negative flags could get
confusing in the future if stat info
is added or adjusted, the file system may then need to make guesses as
to weather or not it should
return this new info, especially if the new info has performance
implications.
The other thing that occurs to me that might be useful is a system
wide stat mask or a shell based stat mask?
I mean lets face it will be very difficult to get all applications
updated to use the stat call such that the "expensive"
stat call that potentially kills your cluster file system performance.
So adding the ability for an administrator to carefully
change the stat mask on critical systems might be a way to actually
realize the benefits of stat lite.
- -Russell Cattelan
Digital Elves Inc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJ294fNRmM+OaGhBgRAs9tAJ9uMnjQW/VEnpJCPDNIQX9hQsvhJgCfWFhZ
uyh+xkYmp5Sxa2T9T4IyEpc=
=7qdU
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-04-07 23:22 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 [this message]
2009-04-07 17:42 ` Jamie Lokier
2009-04-07 17:48 ` Oleg Drokin
2009-04-07 18:16 ` Jamie Lokier
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=49DBDE1F.5070408@thebarn.com \
--to=cattelan@thebarn.com \
--cc=adilger@sun.com \
--cc=linux-fsdevel@vger.kernel.org \
/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).