[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <169559548777.19404.13247796879745924682@noble.neil.brown.name>
Date: Mon, 25 Sep 2023 08:44:47 +1000
From: "NeilBrown" <neilb@...e.de>
To: "Christian Brauner" <brauner@...nel.org>
Cc: "Jeff Layton" <jlayton@...nel.org>,
"Alexander Viro" <viro@...iv.linux.org.uk>,
"Chuck Lever" <chuck.lever@...cle.com>,
"Olga Kornievskaia" <kolga@...app.com>,
"Dai Ngo" <Dai.Ngo@...cle.com>, "Tom Talpey" <tom@...pey.com>,
"Chandan Babu R" <chandan.babu@...cle.com>,
"Darrick J. Wong" <djwong@...nel.org>,
"Dave Chinner" <david@...morbit.com>, "Jan Kara" <jack@...e.cz>,
"Linus Torvalds" <torvalds@...ux-foundation.org>,
"Kent Overstreet" <kent.overstreet@...ux.dev>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-nfs@...r.kernel.org, linux-xfs@...r.kernel.org
Subject: Re: [PATCH v8 0/5] fs: multigrain timestamps for XFS's change_cookie
On Sun, 24 Sep 2023, Christian Brauner wrote:
> > My initial goal was to implement multigrain timestamps on most major
> > filesystems, so we could present them to userland, and use them for
> > NFSv3, etc.
>
> If there's no clear users and workloads depending on this other than for
> the sake of NFS then we shouldn't expose this to userspace. We've tried
> this and I'm not convinced we're getting anything other than regressions
> out of it. Keep it internal and confined to the filesystem that actually
> needs this.
>
Some NFS servers run in userspace, and they would a "clear user" of this
functionality.
NeilBrown
Powered by blists - more mailing lists