There was introduced fc->bg_lock to reduce the contention,
and this patchset continues this efforts.
This patchset introduces per fuse_inode lock to protect
inode metadata, synchronization with background writes, etc.
All of the above is related to a single inode, and there
is no a reason, that inodes are concurrents of each other
to make some of actions exclusive.
So, here we introduce fuse_inode::lock spinlock and get rid
of fc->lock in many places.
---
Kirill Tkhai (6):
fuse: Change argument of fuse_flush_writepages()
fuse: Add fuse_inode argument to fuse_prepare_release()
fuse: Introduce fuse_inode::lock to protect write related fields and statistics
fuse: Implement fuse_attr_version_inc()
fuse: Protect fuse_inode::nlookup with fuse_inode::lock
fuse: Protect fuse_file::reserved_req via corresponding fuse_inode::lock
fs/fuse/cuse.c | 3 +
fs/fuse/dev.c | 10 +++-
fs/fuse/dir.c | 41 +++++++++---------
fs/fuse/file.c | 119 ++++++++++++++++++++++++++++-------------------------
fs/fuse/fuse_i.h | 27 ++++++++++--
fs/fuse/inode.c | 16 ++++---
fs/fuse/readdir.c | 4 +-
7 files changed, 126 insertions(+), 94 deletions(-)
--
Signed-off-by: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
