Return-Path: In-Reply-To: <20131028210247.GM31322@fieldses.org> References: <1382920068.6932.46.camel@heisenberg.scientia.net> <2E672741-FE4F-4287-8D00-B7634A71709E@netapp.com> <526E8562.3040809@redhat.com> <1382976943.8774.10.camel@heisenberg.scientia.net> <526EA65A.7010209@redhat.com> <20131028180838.GG31322@fieldses.org> <526EAD86.6090507@redhat.com>

<20131028210247.GM31322@fieldses.org> To: "J. Bruce Fields" From: Marc Eshel Message-ID: Date: Mon, 28 Oct 2013 14:28:34 -0700 Cc: Mailing List Linux NFS , "Haynes, Tom" , Christoph Anton Mitterer , "nfsv4@ietf.org nfsv4@ietf.org" , Steve Dickson , "Myklebust, Trond" , Ric Wheeler , "linux-nfs-owner@vger.kernel.org" Subject: Re: [nfsv4] XATTRs in NFS? List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6599115206786229813==" Sender: nfsv4-bounces@ietf.org Errors-To: nfsv4-bounces@ietf.org MIME-Version: 1.0 List-ID: --===============6599115206786229813== Content-Type: multipart/alternative; boundary="=_alternative 00754A1988257C12_=" --=_alternative 00754A1988257C12_= Content-Type: text/plain; charset="US-ASCII" "J. Bruce Fields" wrote on 10/28/2013 02:02:47 PM: > From: "J. Bruce Fields" > To: "Haynes, Tom" , > Cc: Marc Eshel/Almaden/IBM@IBMUS, Spencer Shepler > , Mailing List Linux NFS nfs@vger.kernel.org>, Christoph Anton Mitterer > , "Myklebust, Trond" > , Steve Dickson , > "nfsv4@ietf.org nfsv4@ietf.org" , Ric Wheeler > , "linux-nfs-owner@vger.kernel.org" nfs-owner@vger.kernel.org> > Date: 10/28/2013 02:02 PM > Subject: Re: [nfsv4] XATTRs in NFS? > > On Mon, Oct 28, 2013 at 08:55:06PM +0000, Haynes, Tom wrote: > > > > On Oct 28, 2013, at 1:44 PM, Marc Eshel wrote: > > > > > Hi Spencer, > > > Is it still possible to get on the agenda fir IETF 88, I just > got approval > > > to travel. We can use about 15 minutes, or what ever is available to > > > discussion the future of named attributes in NFS. The two main questions > > > that we need answer are: > > > 1. Do we need them? what applications use them and how. > > > 2. Can we have a more simple model that handles just user attributes. > > > > > > Input is welcome to help me make the case at the meeting. > > > > > > Thanks, Marc. > > > > > > > > > Be sure to call out why they currently do or do not work. > > And we also need to keep clear the distinctions between: > > - NFSv4 named attributes/streams/forks and "extended attributes" > as implemented in Linux and elsewhere. > - user.* xattrs and "back-door ioctls". > > (Your description above seems to confuse named attributes and Linux > extended attributes.) Yes, I used user which is the Linux type of xattr but what I meant is somthing like the Linux user attributes with no special meaning to NFS, so NFS can be used to just transfer opaque attributes. Marc. > > --b. > --=_alternative 00754A1988257C12_= Content-Type: text/html; charset="US-ASCII"
"J. Bruce Fields" <bfields@fieldses.org> wrote on 10/28/2013 02:02:47 PM: > From: "J. Bruce Fields" <bfields@fieldses.org>
> To: "Haynes, Tom" <Tom.Haynes@netapp.com>,
> Cc: Marc Eshel/Almaden/IBM@IBMUS, Spencer Shepler > <spencer.shepler@gmail.com>, Mailing List Linux NFS <linux- > nfs@vger.kernel.org>, Christoph Anton Mitterer > <calestyo@scientia.net>, "Myklebust, Trond" > <Trond.Myklebust@netapp.com>, Steve Dickson <SteveD@redhat.com>, > "nfsv4@ietf.org nfsv4@ietf.org" <nfsv4@ietf.org>, Ric Wheeler > <ric.wheeler@usenix.org>, "linux-nfs-owner@vger.kernel.org" <linux- > nfs-owner@vger.kernel.org>
> Date: 10/28/2013 02:02 PM
> Subject: Re: [nfsv4] XATTRs in NFS?
> > On Mon, Oct 28, 2013 at 08:55:06PM +0000, Haynes, Tom wrote: > > > > On Oct 28, 2013, at 1:44 PM, Marc Eshel <eshel@us.ibm.com> wrote: > > > > > Hi Spencer, > > > Is it still possible to get on the agenda fir IETF 88, I just > got approval > > > to travel. We can use about 15 minutes, or what ever is available to > > > discussion the future of named attributes in NFS. The two main questions > > > that we need answer are: > > > 1. Do we need them? what applications use them and how. > > > 2. Can we have a more simple model that handles just user attributes. > > > > > > Input is welcome to help me make the case at the meeting. > > > > > > Thanks, Marc. > > > > > > > > > Be sure to call out why they currently do or do not work. > > And we also need to keep clear the distinctions between: > > - NFSv4 named attributes/streams/forks and "extended attributes" > as implemented in Linux and elsewhere. > - user.* xattrs and "back-door ioctls". > > (Your description above seems to confuse named attributes and Linux > extended attributes.)

Yes, I used user which is the Linux type of xattr but what I meant is somthing like the Linux user attributes with no special meaning to NFS, so NFS can be used to just transfer opaque attributes.
Marc.

> > --b. > --=_alternative 00754A1988257C12_=-- --===============6599115206786229813== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ nfsv4 mailing list nfsv4@ietf.org https://www.ietf.org/mailman/listinfo/nfsv4 --===============6599115206786229813==--