From: Shaohua Li <shli@kernel.org>
To: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Cc: tj@kernel.org, lizefan@huawei.com, tglx@linutronix.de,
kernel-team@fb.com, axboe@kernel.dk, Shaohua Li <shli@fb.com>
Subject: [PATCH V3 0/4] block: make loop block device cgroup aware
Date: Thu, 14 Sep 2017 14:02:03 -0700 [thread overview]
Message-ID: <cover.1505422351.git.shli@fb.com> (raw)
From: Shaohua Li <shli@fb.com>
Hi,
The IO dispatched to under layer disk by loop block device isn't cloned from
original bio, so the IO loses cgroup information of original bio. These IO
escapes from cgroup control. The patches try to address this issue. The idea is
quite generic, but we currently only make it work for blkcg.
Thanks,
Shaohua
V2->V3:
- Make the API more robust pointed out by Tejun
V1->V2:
- Address a couple of issues pointed out by Tejun
Shaohua Li (4):
kthread: add a mechanism to store cgroup info
blkcg: delete unused APIs
block: make blkcg aware of kthread stored original cgroup info
block/loop: make loop cgroup aware
block/bio.c | 31 ----------------------
drivers/block/loop.c | 13 +++++++++
drivers/block/loop.h | 1 +
include/linux/bio.h | 2 --
include/linux/blk-cgroup.h | 25 +++++-------------
include/linux/kthread.h | 11 ++++++++
kernel/kthread.c | 66 ++++++++++++++++++++++++++++++++++++++++++++--
7 files changed, 96 insertions(+), 53 deletions(-)
--
2.9.5
next reply other threads:[~2017-09-14 21:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 21:02 Shaohua Li [this message]
2017-09-14 21:02 ` [PATCH V3 1/4] kthread: add a mechanism to store cgroup info Shaohua Li
2017-09-15 15:51 ` Tejun Heo
2017-09-14 21:02 ` [PATCH V3 2/4] blkcg: delete unused APIs Shaohua Li
2017-09-14 21:02 ` [PATCH V3 3/4] block: make blkcg aware of kthread stored original cgroup info Shaohua Li
2017-09-14 21:02 ` [PATCH V3 4/4] block/loop: make loop cgroup aware Shaohua Li
2017-09-25 16:44 ` [PATCH V3 0/4] block: make loop block device " Shaohua Li
2017-09-25 19:03 ` 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=cover.1505422351.git.shli@fb.com \
--to=shli@kernel.org \
--cc=axboe@kernel.dk \
--cc=kernel-team@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=shli@fb.com \
--cc=tglx@linutronix.de \
--cc=tj@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).