From: Marc Eshel Subject: Re: XATTRs in NFS? Date: Mon, 28 Oct 2013 14:28:35 -0700 Message-ID: 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> <6AB20096-3993-47DD-AB58-2CD25F8A75D8@oracle.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8523528931232107062==" Cc: Mailing List Linux NFS , "Haynes, Tom" , Christoph Anton Mitterer , "nfsv4@ietf.org nfsv4@ietf.org" , Steve Dickson , "J. Bruce Fields" , Ric Wheeler , "Myklebust, Trond" , "linux-nfs-owner@vger.kernel.org" To: Chuck Lever Return-path: In-Reply-To: <6AB20096-3993-47DD-AB58-2CD25F8A75D8@oracle.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nfsv4-bounces@ietf.org Errors-To: nfsv4-bounces@ietf.org List-ID: This is a multipart message in MIME format. --===============8523528931232107062== Content-Type: multipart/alternative; boundary="=_alternative 0075F15C88257C12_=" This is a multipart message in MIME format. --=_alternative 0075F15C88257C12_= Content-Type: text/plain; charset="US-ASCII" linux-nfs-owner@vger.kernel.org wrote on 10/28/2013 02:04:57 PM: > From: Chuck Lever > To: "J. Bruce Fields" , > Cc: "Haynes, Tom" , Marc Eshel/Almaden/ > IBM@IBMUS, Spencer Shepler , Mailing List > Linux NFS , 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:07 PM > Subject: Re: [nfsv4] XATTRs in NFS? > Sent by: linux-nfs-owner@vger.kernel.org > > > On Oct 28, 2013, at 5:02 PM, "J. Bruce Fields" wrote: > > > 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.) > > I wonder if we will have a balanced discussion next week. The > people who seem to know the most about these issues on Linux will > not be attending. Perhaps it would be better to start this > discussion on the mailing list instead. Like I said input is welcome to the mailing list and I can try to collect all the main points into a presentation at the IETF. The main objective for now is to see if this is an item for the working group to start dealing with for future NFS protocol enhancements. Marc. > > -- > Chuck Lever > chuck[dot]lever[at]oracle[dot]com > > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > --=_alternative 0075F15C88257C12_= Content-Type: text/html; charset="US-ASCII"
linux-nfs-owner@vger.kernel.org wrote on 10/28/2013 02:04:57 PM: > From: Chuck Lever <chuck.lever@oracle.com>
> To: "J. Bruce Fields" <bfields@fieldses.org>,
> Cc: "Haynes, Tom" <Tom.Haynes@netapp.com>, 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:07 PM
> Subject: Re: [nfsv4] XATTRs in NFS?
> Sent by: linux-nfs-owner@vger.kernel.org
> > > On Oct 28, 2013, at 5:02 PM, "J. Bruce Fields" <bfields@fieldses.org> wrote: > > > 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.) > > I wonder if we will have a balanced discussion next week. The > people who seem to know the most about these issues on Linux will > not be attending. Perhaps it would be better to start this > discussion on the mailing list instead.

Like I said input is welcome to the mailing list and I can try to collect all the main points into a presentation at the IETF. The main objective for now is to see if this is an item for the working group to start dealing with for future NFS protocol enhancements.
Marc.
> > -- > Chuck Lever > chuck[dot]lever[at]oracle[dot]com > > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html> --=_alternative 0075F15C88257C12_=-- --===============8523528931232107062== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ nfsv4 mailing list nfsv4@ietf.org https://www.ietf.org/mailman/listinfo/nfsv4 --===============8523528931232107062==--