From: Jamie Lokier <jamie@shareable.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: statfs() / statvfs() syscall ballsup...
Date: Fri, 10 Oct 2003 15:39:20 +0100 [thread overview]
Message-ID: <20031010143920.GB28795@mail.shareable.org> (raw)
In-Reply-To: <16262.47147.943477.24070@charged.uio.no>
Trond Myklebust wrote:
> > I don't care about the cache semantics at all; what I care
> > about is whether a returned stat() result may be stale.
>
> Note that this too may be a per-file property.
Yes. A flag from stat() or similar to say it's stale would make
sense. Alternatively, a flag _into_ something like stat() to ask for
an up to date value, if that is possible.
I've often wondered if stat() couldn't be a bit more extensible with
some flags or extended attributes.
-- Jamie
next prev parent reply other threads:[~2003-10-10 14:39 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 22:16 statfs() / statvfs() syscall ballsup Trond Myklebust
2003-10-09 22:26 ` Linus Torvalds
2003-10-09 23:19 ` Ulrich Drepper
2003-10-10 0:22 ` viro
2003-10-10 4:49 ` Jamie Lokier
2003-10-10 5:26 ` Trond Myklebust
2003-10-10 12:37 ` Jamie Lokier
2003-10-10 13:46 ` Trond Myklebust
2003-10-10 14:35 ` Jamie Lokier
2003-10-10 15:32 ` Misc NFSv4 (was Re: statfs() / statvfs() syscall ballsup...) Trond Myklebust
2003-10-10 15:53 ` Jamie Lokier
2003-10-10 16:07 ` Trond Myklebust
2003-10-10 15:55 ` Michael Shuey
2003-10-10 16:20 ` Trond Myklebust
2003-10-10 16:45 ` J. Bruce Fields
2003-10-10 14:39 ` Jamie Lokier [this message]
2003-10-09 23:31 ` statfs() / statvfs() syscall ballsup Trond Myklebust
2003-10-10 12:27 ` Joel Becker
2003-10-10 14:59 ` Linus Torvalds
2003-10-10 15:27 ` Joel Becker
2003-10-10 16:00 ` Linus Torvalds
2003-10-10 16:26 ` Joel Becker
2003-10-10 16:50 ` Linus Torvalds
2003-10-10 17:33 ` Joel Becker
2003-10-10 17:51 ` Linus Torvalds
2003-10-10 18:13 ` Joel Becker
2003-10-10 16:27 ` Valdis.Kletnieks
2003-10-10 16:33 ` Chris Friesen
2003-10-10 17:04 ` Linus Torvalds
2003-10-10 17:07 ` Linus Torvalds
2003-10-10 17:21 ` Joel Becker
2003-10-10 16:01 ` Jamie Lokier
2003-10-10 16:33 ` Joel Becker
2003-10-10 16:58 ` Chris Friesen
2003-10-10 17:05 ` Trond Myklebust
2003-10-10 17:20 ` Joel Becker
2003-10-10 17:33 ` Chris Friesen
2003-10-10 17:40 ` Linus Torvalds
2003-10-10 17:54 ` Trond Myklebust
2003-10-10 18:05 ` Linus Torvalds
2003-10-10 20:40 ` Trond Myklebust
2003-10-10 21:09 ` Linus Torvalds
2003-10-10 22:17 ` Trond Myklebust
2003-10-11 2:53 ` Andrew Morton
2003-10-11 3:47 ` Trond Myklebust
2003-10-10 18:05 ` Joel Becker
2003-10-10 18:31 ` Andrea Arcangeli
2003-10-10 20:33 ` Helge Hafting
2003-10-10 20:07 ` Jamie Lokier
2003-10-12 15:31 ` Greg Stark
2003-10-12 16:13 ` Linus Torvalds
2003-10-12 22:09 ` Greg Stark
2003-10-13 8:45 ` Helge Hafting
2003-10-15 13:25 ` Ingo Oeser
2003-10-15 15:03 ` Greg Stark
2003-10-15 18:37 ` Helge Hafting
2003-10-16 10:29 ` Ingo Oeser
2003-10-16 14:02 ` Greg Stark
2003-10-21 11:47 ` Ingo Oeser
2003-10-10 18:20 ` Andrea Arcangeli
2003-10-10 18:36 ` Linus Torvalds
2003-10-10 19:03 ` Andrea Arcangeli
2003-10-09 23:16 ` Andreas Dilger
2003-10-09 23:24 ` Linus Torvalds
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=20031010143920.GB28795@mail.shareable.org \
--to=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.