From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH v4 0/6] A variety of lock contention fixes
Date: Thu, 17 Dec 2020 09:35:56 -0500 [thread overview]
Message-ID: <cover.1608215552.git.josef@toxicpanda.com> (raw)
v3->v4:
- I accidentally sent out the v1 version of these patches, because I had fixed
them on another machine. This is the proper set with the changes from v2 that
are properly rebased onto misc-next.
v2->v3:
- Added Nikolay's reviewed by for the second patch.
- Rebased onto the latest misc-next.
v1->v2:
- Fixed the log messages that Nikolay pointed out.
- Added Nikolay's reviewed by for the first patch.
- Removed the unneeded mb for flushing.
--- Original email ---
Hello,
I've been running some stress tests recently in order to try and reproduce some
problems I've tripped over in relocation. Most of this series is a reposting of
patches I wrote when debugging related issues for Zygo that got lost. I've
updated one of them to make the lock contention even better, making it so I have
to ramp up my stress test loops because it now finishes way too fast. Thanks,
Josef
Josef Bacik (6):
btrfs: do not block on deleted bgs mutex in the cleaner
btrfs: only let one thread pre-flush delayed refs in commit
btrfs: delayed refs pre-flushing should only run the heads we have
btrfs: only run delayed refs once before committing
btrfs: stop running all delayed refs during snapshot
btrfs: run delayed refs less often in commit_cowonly_roots
fs/btrfs/block-group.c | 11 +++++--
fs/btrfs/delayed-ref.h | 12 +++----
fs/btrfs/extent-tree.c | 2 +-
fs/btrfs/transaction.c | 74 ++++++++++++++++--------------------------
4 files changed, 43 insertions(+), 56 deletions(-)
--
2.26.2
reply other threads:[~2020-12-17 14:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1608215552.git.josef@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=kernel-team@fb.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