From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH v3 0/2] Refactor snapshot vs nocow writers locking
Date: Mon, 24 Feb 2020 17:26:35 +0200 [thread overview]
Message-ID: <20200224152637.30774-1-nborisov@suse.com> (raw)
Here is v3 of the DRW locking patches.
Main changes in this verison:
* Removed EXPORT_SYMBOL for function since I do not intend to submit the locktorture
patch
* Added high-level comment as per David's request.
V2:
* Fixed all checkpatch warnings (Andrea Parri)
* Properly call write_unlock in btrfs_drw_try_write_lock (Filipe Manana)
* Comment fix.
* Stress tested it via locktorture. Survived for 8 straight days on a 4 socket
48 thread machine.
Nikolay Borisov (2):
btrfs: convert snapshot/nocow exlcusion to drw lock
btrfs: Hook btrfs' DRW lock to locktorture infrastructure
fs/btrfs/ctree.h | 9 +----
fs/btrfs/disk-io.c | 46 ++++++---------------
fs/btrfs/extent-tree.c | 44 ---------------------
fs/btrfs/file.c | 11 +++---
fs/btrfs/inode.c | 8 ++--
fs/btrfs/ioctl.c | 10 ++---
fs/btrfs/locking.c | 5 +++
fs/btrfs/locking.h | 1 +
kernel/locking/locktorture.c | 77 +++++++++++++++++++++++++++++++++++-
9 files changed, 107 insertions(+), 104 deletions(-)
--
2.17.1
next reply other threads:[~2020-02-24 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 15:26 Nikolay Borisov [this message]
2020-02-24 15:26 ` [PATCH v3 1/2] btrfs: convert snapshot/nocow exlcusion to drw lock Nikolay Borisov
2020-02-24 15:26 ` [PATCH v3 2/2] btrfs: Hook btrfs' DRW lock to locktorture infrastructure Nikolay Borisov
2020-02-24 15:32 ` Nikolay Borisov
2020-02-24 15:32 ` [PATCH 1/2] btrfs: Implement DRW lock Nikolay Borisov
2020-02-24 16:02 ` [PATCH v3 0/2] Refactor snapshot vs nocow writers locking 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=20200224152637.30774-1-nborisov@suse.com \
--to=nborisov@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.