On Wed, Feb 03, 2021 at 04:03:06PM +0100, Miklos Szeredi wrote: > On Wed, Feb 3, 2021 at 3:56 PM Matthew Wilcox <willy@xxxxxxxxxxxxx> wrote: > > > But let's talk specifics. What does CIFS need to contact the server for? > > Could it be cached earlier? > > I don't understand what CIFS is doing, and I don't really care. This > is the sort of operation where adding a couple of network roundtrips > so that the client can obtain the credentials required to perform the > operation doesn't really matter. We won't have thousands of chattr(1) > calls per second. Incorrect. The xfs utilities can do recursive directory traversal to change things like the project ID across an entire directory tree. Or to change extent size hints. We also have 'xfs_io -c "lsattr -R" ...' and 'lsprog -R' which will do a recursive descent to list the requested attributes of all directories and files in the tree... So, yeah, we do indeed do thousands of these fsxattr based operations a second, sometimes tens of thousands a second or more, and sometimes they are issued in bulk in performance critical paths for container build/deployment operations.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx
