From: Kirill Tkhai <ktkhai@virtuozzo.com>
To: miklos@szeredi.hu, ktkhai@virtuozzo.com, linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/7] fuse: Improve disconnect scheme and avoid taking fpq->lock on hot paths
Date: Tue, 15 Jan 2019 13:19:13 +0300 [thread overview]
Message-ID: <154754701031.4244.8089449938935364463.stgit@localhost.localdomain> (raw)
There is no a reason to set individual FR_ABORTED state
for every request, since fuse_abort_conn() aborts all
unlocked requests at once. FR_ABORTED bit and fpq->io
list just allow fuse_copy_aborted() to end some of requests,
which are in the middle of fuse_dev_do_read() and
fuse_dev_do_write(). But this is not a big deal, since
these functions abort the requests themselves.
This patchset introduces a better scheme for fuse_abort_conn(),
which allows to remove excess flags and fpq->io, and optimizes
hot paths fuse_dev_do_read() and fuse_dev_do_write() by avoiding
taking fpq->lock there.
---
Kirill Tkhai (7):
fuse: Check for fc->connected in fuse_dev_alloc()
fuse: Move flush_bg_queue() up in fuse_abort_conn()
fuse: Drop and reacquire fc->lock in middle of fuse_abort_conn()
fuse: Add fud pointer to struct fuse_copy_state
fuse: Introduce generic fuse_copy_aborted()
fuse: Kill unused FR_ABORTED, FR_LOCKED and FR_PRIVATE flags
fuse: Kill fuse_pqueue::io list and avoid taking fpq->lock on hot paths
fs/fuse/dev.c | 131 ++++++++++++++++--------------------------------------
fs/fuse/fuse_i.h | 20 ++------
fs/fuse/inode.c | 10 ++++
3 files changed, 52 insertions(+), 109 deletions(-)
--
Signed-off-by: Kirill Tkhai <ktkhai@virtuozzo.com>
next reply other threads:[~2019-01-15 10:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 10:19 Kirill Tkhai [this message]
2019-01-15 10:19 ` [PATCH 1/7] fuse: Check for fc->connected in fuse_dev_alloc() Kirill Tkhai
2019-01-18 12:07 ` Miklos Szeredi
2019-01-18 12:28 ` Kirill Tkhai
2019-01-23 9:45 ` Miklos Szeredi
2019-01-23 9:55 ` Kirill Tkhai
2019-01-23 10:24 ` Miklos Szeredi
2019-01-15 10:19 ` [PATCH 2/7] fuse: Move flush_bg_queue() up in fuse_abort_conn() Kirill Tkhai
2019-01-15 10:19 ` [PATCH 3/7] fuse: Drop and reacquire fc->lock in middle of fuse_abort_conn() Kirill Tkhai
2019-01-15 10:19 ` [PATCH 4/7] fuse: Add fud pointer to struct fuse_copy_state Kirill Tkhai
2019-01-15 10:19 ` [PATCH 5/7] fuse: Introduce generic fuse_copy_aborted() Kirill Tkhai
2019-01-17 9:48 ` Miklos Szeredi
2019-01-15 10:19 ` [PATCH 6/7] fuse: Kill unused FR_ABORTED, FR_LOCKED and FR_PRIVATE flags Kirill Tkhai
2019-01-15 10:19 ` [PATCH 7/7] fuse: Kill fuse_pqueue::io list and avoid taking fpq->lock on hot paths Kirill Tkhai
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=154754701031.4244.8089449938935364463.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