On Fri, 2024-07-05 at 10:36 -0400, Mike Snitzer wrote: > On Fri, Jul 05, 2024 at 07:18:29AM -0700, Christoph Hellwig wrote: > > On Fri, Jul 05, 2024 at 10:15:46AM -0400, Mike Snitzer wrote: > > > NFSv3 is needed because NFSv3 is used to initiate IO to NFSv3 > > > knfsd on > > > the same host. > > > > That doesn't really bring is any further. Why is it required? > > > > I think we'll just need to stop this discussion until we have > > reasonable > > documentation of the use cases and assumptions, because without > > that > > we'll get hund up in dead loops. > > It _really_ isn't material to the core capability that localio > provides. > localio supporting NFSv3 is beneficial for NFSv3 users (NFSv3 in > containers). > > Hammerspace needs localio to work with NFSv3 to assist with its "data > movers" that run on the host (using nfs and nfsd). > > Please just remove yourself from the conversation if you cannot make > sense of this. If you'd like to be involved, put the work in to > understand the code and be professional. I disagree wholeheartedly with this statement. Christoph has raised a very valid point. You have _not_ articulated why v3 access is important here. I'm aware of why it is (at least to HS), and I think there are other valid reasons to keep v3 in the mix (as Neil has pointed out). But, that info should be in the cover letter and changelogs. Not everyone has insight into this, and tbqh, my understanding could be wrong. Let's do please try to keep the discussion civil. -- Jeff Layton <jlayton@xxxxxxxxxx>
