On Nov 4, 2013, at 9:05 AM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote: > On Mon, Nov 04, 2013 at 11:46:58AM -0500, J. Bruce Fields wrote: >> Imagine it was me, if it helps. >> >> The important thing is that we understand what should be fixed. > > The important part is how someone got the idea for the pattern writing > and the weird ADBs from The original proposal is http://tools.ietf.org/html/draft-eisler-nfsv4-enterprise-apps-01 and has been somewhat modified in its expression in NFSv4.2. > and why they believe they should overload a > single command for all of them. I believe that file initialization is closer in semantics to COPY_OFFLOAD than it is to WRITE, and I find it awkward to use the WRITE_PLUS operation for initialization. But I could never make a strong technical argument why they should not be joined, other than "Clutter!". > And apparently reqular data writes as > well, even if I haven't found that part of the spec yet. http://www.ietf.org/id/draft-ietf-nfsv4-minorversion2-20.txt is the latest version I can find. The usual process is to explain what needs to be fixed (ie, make a problem statement) as Bruce said. That is often accompanied by an alternate design proposal that addresses your issues. It is appropriate to address your comments to the group, and not to a single person. As in most online communities, ad hominem and confrontation are not appreciated. -- 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
