From: Kirill Tkhai <ktkhai@virtuozzo.com>
To: miklos@szeredi.hu, ktkhai@virtuozzo.com, linux-fsdevel@vger.kernel.org
Subject: [PATCH v2 0/5] fuse: Further reducing contention of fc->lock
Date: Fri, 09 Nov 2018 13:33:06 +0300 [thread overview]
Message-ID: <154175935554.21228.11270624605198037428.stgit@localhost.localdomain> (raw)
v2: Removed patch [1/6] from v1, and [4/6] from v1 is replaced
with new patch (which is [2/5] in this v2).
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 (5):
fuse: Add fuse_inode argument to fuse_prepare_release()
fuse: Convert fuse_conn::attr_version into atomic64_t
fuse: Introduce fuse_inode::lock to protect write related fields and statistics
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 | 54 ++++++++++----------------
fs/fuse/file.c | 111 ++++++++++++++++++++++++++++-------------------------
fs/fuse/fuse_i.h | 23 ++++++++---
fs/fuse/inode.c | 17 +++++---
fs/fuse/readdir.c | 4 +-
7 files changed, 115 insertions(+), 107 deletions(-)
--
Signed-off-by: Kirill Tkhai <ktkhai@virtuozzo.com>
next reply other threads:[~2018-11-09 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 10:33 Kirill Tkhai [this message]
2018-11-09 10:33 ` [PATCH v2 1/5] fuse: Add fuse_inode argument to fuse_prepare_release() Kirill Tkhai
2018-11-09 10:33 ` [PATCH v2 2/5] fuse: Convert fuse_conn::attr_version into atomic64_t Kirill Tkhai
2018-11-09 10:33 ` [PATCH v2 3/5] fuse: Introduce fuse_inode::lock to protect write related fields and statistics Kirill Tkhai
2018-11-09 10:33 ` [PATCH v2 4/5] fuse: Protect fuse_inode::nlookup with fuse_inode::lock Kirill Tkhai
2018-11-09 10:33 ` [PATCH v2 5/5] fuse: Protect fuse_file::reserved_req via corresponding fuse_inode::lock Kirill Tkhai
2018-12-10 16:20 ` [PATCH v2 0/5] fuse: Further reducing contention of fc->lock Kirill Tkhai
2019-01-10 8:38 ` Miklos Szeredi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=154175935554.21228.11270624605198037428.stgit@localhost.localdomain \
--to=ktkhai@virtuozzo.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).