From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/4] Replace custom device-replace locking with rwsem
Date: Tue, 20 Nov 2018 13:50:54 +0100 [thread overview]
Message-ID: <cover.1542717531.git.dsterba@suse.com> (raw)
The first cleanup part went to 4.19, the actual switch from the custom
locking to rswem was postponed as I found performance degradation. This
turned out to be related to VM cache settings, so I'm resending the
series again.
The custom locking is based on rwlock protected reader/writer counters,
waitqueues, which essentially is what the readwrite semaphore does.
Previous patchset:
https://lore.kernel.org/linux-btrfs/cover.1536331604.git.dsterba@suse.com/
Patches correspond to 8/11-11/11 and there's no change besides
refreshing on top of current misc-next.
David Sterba (4):
btrfs: reada: reorder dev-replace locks before radix tree preload
btrfs: dev-replace: swich locking to rw semaphore
btrfs: dev-replace: remove custom read/write blocking scheme
btrfs: dev-replace: open code trivial locking helpers
fs/btrfs/ctree.h | 4 +-
fs/btrfs/dev-replace.c | 97 ++++++++++++++----------------------------
fs/btrfs/dev-replace.h | 5 ---
fs/btrfs/disk-io.c | 4 +-
fs/btrfs/reada.c | 16 ++++---
fs/btrfs/scrub.c | 15 ++++---
fs/btrfs/volumes.c | 27 ++++++------
7 files changed, 63 insertions(+), 105 deletions(-)
--
2.19.1
next reply other threads:[~2018-11-20 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 12:50 David Sterba [this message]
2018-11-20 12:50 ` [PATCH 1/4] btrfs: reada: reorder dev-replace locks before radix tree preload David Sterba
2018-11-20 12:51 ` [PATCH 2/4] btrfs: dev-replace: swich locking to rw semaphore David Sterba
2018-11-20 12:51 ` [PATCH 3/4] btrfs: dev-replace: remove custom read/write blocking scheme David Sterba
2018-11-20 12:51 ` [PATCH 4/4] btrfs: dev-replace: open code trivial locking helpers David Sterba
2018-12-03 17:14 ` [PATCH 0/4] Replace custom device-replace locking with rwsem David Sterba
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=cover.1542717531.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
/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).