From: Paolo Valente <paolo.valente@linaro.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
ulf.hansson@linaro.org, linus.walleij@linaro.org,
bfq-iosched@googlegroups.com, oleksandr@natalenko.name,
Tejun Heo <tj@kernel.org>,
cgroups@vger.kernel.org, Paolo Valente <paolo.valente@linaro.org>
Subject: [PATCH 0/2 block/for-next] block, blkcg, bfq: make bfq disable iocost and delete bfq prefix from cgroup filenames
Date: Tue, 17 Sep 2019 18:51:46 +0200 [thread overview]
Message-ID: <20190917165148.19146-1-paolo.valente@linaro.org> (raw)
Hi Jens,
here is the pair of patches from [1] and [2].
Thanks,
Paolo
[1] https://lkml.org/lkml/2019/9/16/469
[2] https://lore.kernel.org/linux-block/20190917151334.GI3084169@devbig004.ftw2.facebook.com/
Angelo Ruocco (1):
block, bfq: delete "bfq" prefix from cgroup filenames
Tejun Heo (1):
blkcg: Make bfq disable iocost when enabled
Documentation/admin-guide/cgroup-v2.rst | 8 +++--
block/bfq-cgroup.c | 48 +++++++++++++------------
block/bfq-iosched.c | 32 +++++++++++++++++
block/blk-iocost.c | 5 ++-
include/linux/blk-cgroup.h | 5 +++
kernel/cgroup/cgroup.c | 2 ++
6 files changed, 71 insertions(+), 29 deletions(-)
--
2.20.1
next reply other threads:[~2019-09-17 16:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 16:51 Paolo Valente [this message]
2019-09-17 16:51 ` [PATCH 1/2] blkcg: Make bfq disable iocost when enabled Paolo Valente
2019-09-17 16:51 ` [PATCH 2/2] block, bfq: delete "bfq" prefix from cgroup filenames Paolo Valente
2019-09-17 21:04 ` Chaitanya Kulkarni
2019-09-17 21:32 ` Tejun Heo
2019-09-18 5:18 ` Paolo Valente
2019-09-18 15:19 ` Tejun Heo
2019-09-18 16:19 ` Paolo Valente
2019-09-20 6:58 ` Paolo Valente
2019-09-20 13:05 ` Jens Axboe
2019-09-21 6:55 ` Paolo Valente
2019-09-18 6:09 ` Ulf Hansson
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=20190917165148.19146-1-paolo.valente@linaro.org \
--to=paolo.valente@linaro.org \
--cc=axboe@kernel.dk \
--cc=bfq-iosched@googlegroups.com \
--cc=cgroups@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr@natalenko.name \
--cc=tj@kernel.org \
--cc=ulf.hansson@linaro.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).