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 V2 1/4] kthread: add a mechanism to store cgroup info
Date: Wed, 13 Sep 2017 14:38:20 -0700 [thread overview]
Message-ID: <20170913213820.GA378890@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <802ba16bd896e56bc974780e97157760fde7c273.1505335620.git.shli@fb.com>
Hello,
On Wed, Sep 13, 2017 at 02:01:26PM -0700, Shaohua Li wrote:
> diff --git a/kernel/kthread.c b/kernel/kthread.c
> index 26db528..3107eee 100644
> --- a/kernel/kthread.c
> +++ b/kernel/kthread.c
> @@ -20,7 +20,6 @@
> #include <linux/freezer.h>
> #include <linux/ptrace.h>
> #include <linux/uaccess.h>
> -#include <linux/cgroup.h>
> #include <trace/events/sched.h>
>
> static DEFINE_SPINLOCK(kthread_create_lock);
> @@ -47,6 +46,7 @@ struct kthread {
> void *data;
> struct completion parked;
> struct completion exited;
maybe #ifdef CONFIG_CGROUPS?
> + struct cgroup_subsys_state *blkcg_css;
> };
...
> +void kthread_associate_blkcg(struct cgroup_subsys_state *css)
> +{
> + struct kthread *kthread;
> +
> + if (!(current->flags & PF_KTHREAD) || !current->set_child_tid)
> + return;
> + kthread = to_kthread(current);
> + if (css) {
> + css_get(css);
> + kthread->blkcg_css = css;
> + } else if (kthread->blkcg_css) {
> + css_put(kthread->blkcg_css);
> + kthread->blkcg_css = NULL;
> + }
> +}
> +EXPORT_SYMBOL(kthread_associate_blkcg);
Maybe doing sth like the following is less error-prone?
kthread_associate_blkcg(@css)
{
if (current's kthread->blkcg_css)
put kthread->blkcg_css and set it to NULL;
if (@css)
get @css and set kthread->blkcg;
}
Thanks.
--
tejun
next prev parent reply other threads:[~2017-09-13 21:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 21:01 [PATCH V2 0/4] block: make loop block device cgroup aware Shaohua Li
2017-09-13 21:01 ` [PATCH V2 1/4] kthread: add a mechanism to store cgroup info Shaohua Li
2017-09-13 21:38 ` Tejun Heo [this message]
2017-09-13 21:43 ` Tejun Heo
2017-09-13 22:30 ` Shaohua Li
2017-09-13 21:01 ` [PATCH V2 2/4] blkcg: delete unused APIs Shaohua Li
2017-09-13 21:40 ` Tejun Heo
2017-09-13 21:01 ` [PATCH V2 3/4] block: make blkcg aware of kthread stored original cgroup info Shaohua Li
2017-09-13 21:42 ` Tejun Heo
2017-09-13 21:01 ` [PATCH V2 4/4] block/loop: make loop cgroup aware Shaohua Li
2017-09-13 21:42 ` Tejun Heo
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=20170913213820.GA378890@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