From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ulrich Drepper Subject: Re: NFSv4/pNFS possible POSIX I/O API standards Date: Wed, 06 Dec 2006 09:19:44 -0800 Message-ID: <4576FBB0.2070704@redhat.com> References: <20061203015203.GA5656@schatzie.adilger.int> <20061204073200.GB5637@schatzie.adilger.int> <1165245336.711.176.camel@lade.trondhjem.org> <4574C48A.8030007@mcs.anl.gov> <1165298200.5776.26.camel@lade.trondhjem.org> <20061205100748.GC5871@infradead.org> <4575E9B0.3060908@mcs.anl.gov> <20061205220538.GA1988@infradead.org> <45760702.6040805@redhat.com> <20061206100614.GX5937@schatzie.adilger.int> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mx1.redhat.com ([66.187.233.31]:37673 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936499AbWLFRVl (ORCPT ); Wed, 6 Dec 2006 12:21:41 -0500 To: Ulrich Drepper , Christoph Hellwig , Rob Ross , Trond Myklebust , Sage Weil , Brad Boyer , Anton Altaparmakov , Gary Grider , linux-fsdevel@vger.kernel.org In-Reply-To: <20061206100614.GX5937@schatzie.adilger.int> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Andreas Dilger wrote: > Does this mean you are against the statlite() API entirely, or only a= gainst > the document's use of the flag as a vague "accuracy" value instead of= a > hard "valid" value? I'm against fuzzy values. I've no problems with a bitmap specifying=20 that certain members are not wanted or wanted (probably the later, zero= =20 meaning the optional fields are not wanted). > IMHO, if the application doesn't need a particular field (e.g. "ls -i= " > doesn't need size, "ls -s" doesn't need the inode number, etc) why sh= ould > these be filled in if they are not easily accessible? As for what is > easily accessible, that needs to be determined by the filesystem itse= lf. Is the size not easily accessible? It would surprise me. If yes, then= ,=20 by all means add it to the list. I'm not against extending the list of= =20 members which are optional if it makes sense. But certain information=20 is certainly always easily accessible. > That was previously suggested by me already. IMHO, there should ONLY= be > a statlite variant of readdirplus(), and I think most people agree wi= th > that part of it (though there is contention on whether readdirplus() = is > needed at all). Indeed. Given there is statlite and we have d_type information, in mos= t=20 situations we won't need more complete stat information. Outside of=20 programs like ls that is. Part of why I wished the lab guys had submitted the draft to the=20 OpenGroup first is that this way they would have to be more detailed on= =20 why each and every interface they propose for adding is really needed.=20 Maybe they can do it now and here. What programs really require=20 readdirplus? --=20 =E2=9E=A7 Ulrich Drepper =E2=9E=A7 Red Hat, Inc. =E2=9E=A7 444 Castro S= t =E2=9E=A7 Mountain View, CA =E2=9D=96 - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html