From: Tejun Heo <tj@kernel.org>
To: Shaohua Li <shli@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
lizefan@huawei.com, tglx@linutronix.de, kernel-team@fb.com,
axboe@kernel.dk, Shaohua Li <shli@fb.com>
Subject: Re: [PATCH V3 1/4] kthread: add a mechanism to store cgroup info
Date: Fri, 15 Sep 2017 08:51:15 -0700 [thread overview]
Message-ID: <20170915155115.GG378890@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <9649525546c2a69f22c7ec5a87858affece87160.1505422351.git.shli@fb.com>
On Thu, Sep 14, 2017 at 02:02:04PM -0700, Shaohua Li wrote:
> From: Shaohua Li <shli@fb.com>
>
> kthread usually runs jobs on behalf of other threads. The jobs should be
> charged to cgroup of original threads. But the jobs run in a kthread,
> where we lose the cgroup context of original threads. The patch adds a
> machanism to record cgroup info of original threads in kthread context.
> Later we can retrieve the cgroup info and attach the cgroup info to jobs.
>
> Since this mechanism is only required by kthread, we store the cgroup
> info in kthread data instead of generic task_struct.
>
> Signed-off-by: Shaohua Li <shli@fb.com>
Acked-by: Tejun Heo <tj@kernel.org>
Thanks.
--
tejun
next prev parent reply other threads:[~2017-09-15 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 21:02 [PATCH V3 0/4] block: make loop block device cgroup aware Shaohua Li
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 [this message]
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=20170915155115.GG378890@devbig577.frc2.facebook.com \
--to=tj@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=shli@kernel.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome