From: Jeff Garzik <jeff@garzik.org>
To: Jamie Lokier <jamie@shareable.org>
Cc: Oleg Drokin <green@linuxhacker.ru>,
linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Attempt at "stat light" implementation
Date: Tue, 07 Apr 2009 13:38:22 -0400 [thread overview]
Message-ID: <49DB8F8E.9010605@garzik.org> (raw)
In-Reply-To: <20090407173248.GC31824@shareable.org>
Jamie Lokier wrote:
> Once you have fine-grained selection of stat fields - it's natural to
> ask why not allow _additional_ stat fields in an future-extensible
> fashion? A few things would be handy sometimes, such as inode
> generation number, modification generation number (to detect changes
> across reboots), and extra flags indicating COW or other properties.
That's quite an interesting thought... until you run out of flags, the
stat structure becomes a bit more flexible.
Jeff
next parent reply other threads:[~2009-04-07 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090407062356.GA1336463@fiona.linuxhacker.ru>
[not found] ` <20090407173248.GC31824@shareable.org>
2009-04-07 17:38 ` Jeff Garzik [this message]
2009-04-07 17:56 ` Attempt at "stat light" implementation Jamie Lokier
2009-04-07 18:21 ` Andreas Dilger
2009-04-07 19:30 ` Ulrich Drepper
2009-04-12 20:55 ` Jamie Lokier
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=49DB8F8E.9010605@garzik.org \
--to=jeff@garzik.org \
--cc=green@linuxhacker.ru \
--cc=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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