s3:vfs_fileid: introduce 'fileid:nolock_max_slots'
authorStefan Metzmacher <metze@samba.org>
Wed, 29 Jun 2022 15:09:51 +0000 (17:09 +0200)
committerRalph Boehme <slow@samba.org>
Tue, 5 Jul 2022 15:09:35 +0000 (15:09 +0000)
commitc040b811eb2b866184cde18145b4a14f249792c9
tree0dcffcd75a984d9c45270786c5f2ce5026cf8505
parentf99b617c0c0cb4ffa52d8ac0732b8600974693d0
s3:vfs_fileid: introduce 'fileid:nolock_max_slots'

This controlls the maximum number of concurrent locking slots
on each host. It specifies the maximal number of locking.tdb
records for a single inode.

It can be used to deliberately break lock coherency not
only between cluster nodes, but also between processes on
each node.

This allows administrators to control the behavior that's
currently only available by 'fsname_norootdir_ext' to
other cases as well.

Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Ralph Boehme <slow@samba.org>
source3/modules/vfs_fileid.c