From: Tejun Heo <tj@kernel.org>
To: axboe@kernel.dk
Cc: shli@kernel.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com, lizefan@huawei.com, hannes@cmpxchg.org,
cgroups@vger.kernel.org, guro@fb.com
Subject: [PATCHSET] blkcg: basic accounting and throttling fixes
Date: Sun, 12 Nov 2017 14:26:06 -0800 [thread overview]
Message-ID: <20171112222613.3613362-1-tj@kernel.org> (raw)
blkcg was often getting basic accounting numbers wildly wrong and
blk-throtl could throttle the same bio multiple times leading to
significantly lower limits being enforced than configured.
This patchset contains the following seven patches to update request
cgroup membership tracking and fix the bugs.
0001-blkcg-relocate-__blkg_release_rcu.patch
0002-blkcg-use-percpu_ref-for-blkcg_gq-refcnt.patch
0003-blkcg-associate-a-request-with-its-blkcg_gq-instead-.patch
0004-blkcg-refactor-blkcg_gq-lookup-and-creation-in-blkcg.patch
0005-blkcg-associate-blk-mq-requests-with-the-matching-bl.patch
0006-blkcg-account-requests-instead-of-bios-for-request-b.patch
0007-blk-throtl-don-t-throttle-the-same-IO-multiple-times.patch
0001-0005 update request cgroup membership tracking so that the
association is always available.
0006 makes blkcg account requests instead of bios as bios don't really
have much to do with what's going on the system.
0007 prevents blk-throttle from throttling the same IO multiple times.
The patches are also available in the following git branch.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git review-blkcg-fixes
diffstat follows. Thanks.
block/blk-cgroup.c | 69 +++++++++++++----------
block/blk-core.c | 13 +++-
block/blk-mq.c | 9 ++-
block/blk-mq.h | 1
block/blk-throttle.c | 10 ---
include/linux/blk-cgroup.h | 134 ++++++++++++++++++++++++++++++++++++---------
include/linux/blkdev.h | 2
7 files changed, 169 insertions(+), 69 deletions(-)
--
tejun
next reply other threads:[~2017-11-12 22:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 22:26 Tejun Heo [this message]
2017-11-12 22:26 ` [PATCH 1/7] blkcg: relocate __blkg_release_rcu() Tejun Heo
2017-11-14 23:12 ` Shaohua Li
2017-11-12 22:26 ` [PATCH 2/7] blkcg: use percpu_ref for blkcg_gq->refcnt Tejun Heo
2017-11-14 23:12 ` Shaohua Li
2017-11-12 22:26 ` [PATCH 3/7] blkcg: associate a request with its blkcg_gq instead of request_list Tejun Heo
2017-11-13 20:15 ` [PATCH v2 " Tejun Heo
2017-11-14 23:17 ` Shaohua Li
2017-11-15 17:11 ` Tejun Heo
2017-11-12 22:26 ` [PATCH 4/7] blkcg: refactor blkcg_gq lookup and creation in blkcg_bio_issue_check() Tejun Heo
2017-11-14 23:18 ` Shaohua Li
2017-11-12 22:26 ` [PATCH 5/7] blkcg: associate blk-mq requests with the matching blkcg_gqs Tejun Heo
2017-11-12 22:26 ` [PATCH 6/7] blkcg: account requests instead of bios for request based request_queues Tejun Heo
2017-11-14 23:23 ` Shaohua Li
2017-11-15 17:18 ` [PATCH v2 " Tejun Heo
2017-11-15 17:19 ` [PATCH " Jens Axboe
2017-11-15 17:22 ` [PATCH v3 " Tejun Heo
2017-11-12 22:26 ` [PATCH 7/7] blk-throtl: don't throttle the same IO multiple times Tejun Heo
2017-11-13 4:07 ` Shaohua Li
2017-11-13 11:13 ` Tejun Heo
2017-11-13 15:57 ` Tejun Heo
2017-11-13 19:54 ` Shaohua Li
2017-11-13 19:58 ` Tejun Heo
2017-11-13 19:58 ` Shaohua Li
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=20171112222613.3613362-1-tj@kernel.org \
--to=tj@kernel.org \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=shli@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