From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fieldses.org ([173.255.197.46]:33868 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750787AbdAMRQR (ORCPT ); Fri, 13 Jan 2017 12:16:17 -0500 Date: Fri, 13 Jan 2017 12:16:16 -0500 To: David Howells Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org Subject: Re: [LSF/MM TOPIC] Network filesystem cache management system call Message-ID: <20170113171616.GG24709@fieldses.org> References: <12324.1483742446@warthog.procyon.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <12324.1483742446@warthog.procyon.org.uk> From: bfields@fieldses.org (J. Bruce Fields) Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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.