From: Tejun Heo <tj@kernel.org>
To: josef@toxicpanda.com, clm@fb.com, dsterba@suse.com
Cc: axboe@kernel.dk, jack@suse.cz, linux-kernel@vger.kernel.org,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCHSET v3 btrfs/for-next] btrfs: fix cgroup writeback support
Date: Wed, 10 Jul 2019 12:28:13 -0700 [thread overview]
Message-ID: <20190710192818.1069475-1-tj@kernel.org> (raw)
Hello,
This patchset contains only the btrfs part of the following patchset.
[1] [PATCHSET v2 btrfs/for-next] blkcg, btrfs: fix cgroup writeback support
The block part has already been applied to
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/ for-linus
with some naming changes. This patchset has been updated accordingly.
When writeback is executed asynchronously (e.g. for compression), bios
are bounced to and issued by worker pool shared by all cgroups. This
leads to significant priority inversions when cgroup IO control is in
use - IOs for a low priority cgroup can tie down the workers forcing
higher priority IOs to wait behind them.
This patchset updates btrfs to issue async IOs through the new bio
punt mechanism. A bio tagged with REQ_CGROUP_PUNT flag is bounced to
the asynchronous issue context of the associated blkcg on
bio_submit(). As the bios are issued from per-blkcg work items,
there's no concern for priority inversions and it doesn't require
invasive changes to the filesystems.
This patchset contains the following 5 patches.
0001-Btrfs-stop-using-btrfs_schedule_bio.patch
0002-Btrfs-delete-the-entire-async-bio-submission-framewo.patch
0003-Btrfs-only-associate-the-locked-page-with-one-async_.patch
0004-Btrfs-use-REQ_CGROUP_PUNT-for-worker-thread-submitte.patch
0005-Btrfs-extent_write_locked_range-should-attach-inode-.patch
The patches are also available in the following branch.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git review-btrfs-cgroup-updates-v3
Thanks, diffstat follows.
fs/btrfs/compression.c | 16 ++
fs/btrfs/compression.h | 3
fs/btrfs/ctree.h | 1
fs/btrfs/disk-io.c | 25 +---
fs/btrfs/extent_io.c | 15 +-
fs/btrfs/inode.c | 62 +++++++++--
fs/btrfs/super.c | 1
fs/btrfs/volumes.c | 264 -------------------------------------------------
fs/btrfs/volumes.h | 10 -
9 files changed, 90 insertions(+), 307 deletions(-)
--
tejun
[1] http://lkml.kernel.org/r/20190615182453.843275-1-tj@kernel.org
next reply other threads:[~2019-07-10 19:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 19:28 Tejun Heo [this message]
2019-07-10 19:28 ` [PATCH 1/5] Btrfs: stop using btrfs_schedule_bio() Tejun Heo
2019-07-11 11:32 ` Nikolay Borisov
2019-07-10 19:28 ` [PATCH 2/5] Btrfs: delete the entire async bio submission framework Tejun Heo
2019-07-11 14:53 ` Nikolay Borisov
2019-07-10 19:28 ` [PATCH 3/5] Btrfs: only associate the locked page with one async_cow struct Tejun Heo
2019-07-11 16:00 ` Nikolay Borisov
2019-07-11 19:52 ` Chris Mason
2019-07-26 15:29 ` Nikolay Borisov
2019-07-10 19:28 ` [PATCH 4/5] Btrfs: use REQ_CGROUP_PUNT for worker thread submitted bios Tejun Heo
2019-07-10 19:28 ` [PATCH 5/5] Btrfs: extent_write_locked_range() should attach inode->i_wb Tejun Heo
2019-07-26 15:13 ` [PATCHSET v3 btrfs/for-next] btrfs: fix cgroup writeback support David Sterba
2019-09-05 11:59 ` David Sterba
2019-09-06 17:46 ` Tejun Heo
2019-10-02 14:15 ` 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=20190710192818.1069475-1-tj@kernel.org \
--to=tj@kernel.org \
--cc=axboe@kernel.dk \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jack@suse.cz \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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).