From: bfields@fieldses.org (J. Bruce Fields)
To: David Howells <dhowells@redhat.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org
Subject: Re: [LSF/MM TOPIC] Network filesystem cache management system call
Date: Fri, 13 Jan 2017 12:16:16 -0500 [thread overview]
Message-ID: <20170113171616.GG24709@fieldses.org> (raw)
In-Reply-To: <12324.1483742446@warthog.procyon.org.uk>
On Fri, Jan 06, 2017 at 10:40:46PM +0000, David Howells wrote:
> AFS filesystem implementations like OpenAFS have a number of management calls
> usually implemented through the pioctl() and afs() system calls. However,
> there is general revulsion to the idea of allowing these in Linux as they are
> very much abused.
>
> Now, I need to come up with replacements for these. For some I can use
> getxattr()/setxattr(), for some keyrings and for others procfs/sysfs, but for
> some I can't.
>
> One of these is the call to manage local caching on a file or volume. This,
> however, doesn't really need to be limited to AFS, but could also be
> applicable to NFS, CIFS, etc. - and possibly even to local filesystems.
Do you have a summary of the AFS interface to give an idea what's
needed?
--b.
next prev parent reply other threads:[~2017-01-13 17:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 22:40 [LSF/MM TOPIC] Network filesystem cache management system call David Howells
2017-01-06 23:18 ` Andreas Dilger
2017-01-07 14:27 ` [Lsf-pc] " Jeff Layton
2017-01-13 17:16 ` J. Bruce Fields [this message]
2017-01-17 16:42 ` David Howells
2017-01-20 16:53 ` [Lsf-pc] " Jeff Layton
2017-01-20 17:45 ` David Howells
2017-01-20 18:08 ` Jeff Layton
2017-01-15 23:36 ` Oleg Drokin
2017-01-17 16:49 ` David Howells
2017-01-18 20:12 ` Jeffrey Altman
2017-01-19 14:48 ` David Howells
2017-01-20 4:32 ` Jeffrey Altman
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=20170113171616.GG24709@fieldses.org \
--to=bfields@fieldses.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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 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.