From: Tejun Heo <tj@kernel.org>
To: axboe@kernel.dk, jbacik@fb.com
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
kernel-team@fb.com, dennis@kernel.org, jack@suse.cz
Subject: [PATCHSET block/for-linus] Assorted blkcg fixes
Date: Thu, 13 Jun 2019 15:30:36 -0700 [thread overview]
Message-ID: <20190613223041.606735-1-tj@kernel.org> (raw)
Hello,
This patchset contains the following blkcg fixes.
0001-blk-iolatency-clear-use_delay-when-io.latency-is-set.patch
0002-blkcg-update-blkcg_print_stat-to-handle-larger-outpu.patch
0003-blkcg-perpcu_ref-init-exit-should-be-done-from-blkg_.patch
0004-blkcg-blkcg_activate_policy-should-initialize-ancest.patch
0005-blkcg-writeback-dead-memcgs-shouldn-t-contribute-to-.patch
Please refer to each patch's description for details. Patchset is
also available in the following git branch.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git review-blkcg-fixes
Thanks. diffstat follows.
block/blk-cgroup.c | 24 ++++++++++++------------
block/blk-iolatency.c | 4 +++-
fs/fs-writeback.c | 8 +++++++-
3 files changed, 22 insertions(+), 14 deletions(-)
--
tejun
next reply other threads:[~2019-06-13 22:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 22:30 Tejun Heo [this message]
2019-06-13 22:30 ` [PATCH 1/5] blk-iolatency: clear use_delay when io.latency is set to zero Tejun Heo
2019-06-13 22:30 ` [PATCH 2/5] blkcg: update blkcg_print_stat() to handle larger outputs Tejun Heo
2019-06-13 22:30 ` [PATCH 3/5] blkcg: perpcu_ref init/exit should be done from blkg_alloc/free() Tejun Heo
2019-06-13 22:30 ` [PATCH 4/5] blkcg: blkcg_activate_policy() should initialize ancestors first Tejun Heo
2019-06-13 22:30 ` [PATCH 5/5] blkcg, writeback: dead memcgs shouldn't contribute to writeback ownership arbitration Tejun Heo
2019-06-19 11:20 ` Jan Kara
2019-06-15 7:40 ` [PATCHSET block/for-linus] Assorted blkcg fixes Jens Axboe
2019-06-15 15:50 ` Tejun Heo
2019-06-15 16:40 ` Jens Axboe
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=20190613223041.606735-1-tj@kernel.org \
--to=tj@kernel.org \
--cc=axboe@kernel.dk \
--cc=dennis@kernel.org \
--cc=jack@suse.cz \
--cc=jbacik@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-block@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).