On Tue, Feb 27, 2024 at 7:46 PM Darrick J. Wong <djwong@xxxxxxxxxx> wrote: > > From: Darrick J. Wong <djwong@xxxxxxxxxx> > > To head off bikeshedding about the fields in xfs_commit_range, let's > make it an opaque u64 array and require the userspace program to call > a third ioctl to sample the freshness data for us. If we ever converge > on a definition for i_version then we can use that; for now we'll just > use mtime/ctime like the old swapext ioctl. This addresses my concerns about using mtime/ctime. I have to say, Darrick, that I think that referring to this concern as bikeshedding is not being honest. I do hate nit picking reviews and I do hate "maybe also fix the world" review comments, but I think the question about using mtime/ctime in this new API was not out of place and I think that making the freshness data opaque is better for everyone in the long run and hopefully, this will help you move to the things you care about faster. Thanks, Amir.
