From: Tejun Heo <tj@kernel.org>
To: Shaohua Li <shli@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
gregkh@linuxfoundation.org, hch@lst.de, axboe@fb.com,
rostedt@goodmis.org, lizefan@huawei.com, Kernel-team@fb.com,
Shaohua Li <shli@fb.com>
Subject: Re: [PATCH V3 11/12] blktrace: add an option to allow displying cgroup path
Date: Mon, 19 Jun 2017 15:14:46 -0400 [thread overview]
Message-ID: <20170619191446.GM12062@htj.duckdns.org> (raw)
In-Reply-To: <6943a743192fd1ceb591e60fa02e5347f0320b18.1497549993.git.shli@fb.com>
Hello,
On Thu, Jun 15, 2017 at 11:17:19AM -0700, Shaohua Li wrote:
> From: Shaohua Li <shli@fb.com>
>
> By default we output cgroup id in blktrace. This adds an option to
> display cgroup path. Since get cgroup path is a relativly heavy
> operation, we don't enable it by default.
>
> with the option enabled, blktrace will output something like this:
> dd-1353 [007] d..2 293.015252: 8,0 /test/level D R 24 + 8 [dd]
>
> Signed-off-by: Shaohua Li <shli@fb.com>
> @@ -613,6 +613,9 @@ static inline struct kernfs_node_id *cgroup_get_node_id(struct cgroup *cgrp)
> {
> return &cgrp->kn->id;
> }
> +
> +void cgroup_path_from_node_id(const struct kernfs_node_id *id,
> + char *buf, size_t buflen);
Maybe cgroup_path_from_kernfs_id()? We eventually can replace
cgrp->id w/ kernfs id and drop the kernfs qualifier.
Thanks.
--
tejun
next prev parent reply other threads:[~2017-06-19 19:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 18:17 [PATCH V3 00/12] blktrace: output cgroup info Shaohua Li
2017-06-15 18:17 ` [PATCH V3 01/12] kernfs: use idr instead of ida to manage inode number Shaohua Li
2017-06-19 18:52 ` Tejun Heo
2017-06-15 18:17 ` [PATCH V3 02/12] kernfs: implement i_generation Shaohua Li
2017-06-19 18:52 ` Tejun Heo
2017-06-15 18:17 ` [PATCH V3 03/12] kernfs: add an API to get kernfs node from inode number Shaohua Li
2017-06-19 18:59 ` Tejun Heo
2017-06-15 18:17 ` [PATCH V3 04/12] kernfs: don't set dentry->d_fsdata Shaohua Li
2017-06-19 19:00 ` Tejun Heo
2017-06-15 18:17 ` [PATCH V3 05/12] kernfs: introduce kernfs_node_id Shaohua Li
2017-06-16 14:42 ` kbuild test robot
2017-06-19 19:01 ` Tejun Heo
2017-06-15 18:17 ` [PATCH V3 06/12] kernfs: add exportfs operations Shaohua Li
2017-06-19 19:07 ` Tejun Heo
2017-06-15 18:17 ` [PATCH V3 07/12] cgroup: export fhandle info for a cgroup Shaohua Li
2017-06-15 18:17 ` [PATCH V3 08/12] blktrace: export cgroup info in trace Shaohua Li
2017-06-15 18:17 ` [PATCH V3 09/12] block: always attach cgroup info into bio Shaohua Li
2017-06-19 19:09 ` Tejun Heo
2017-06-15 18:17 ` [PATCH V3 10/12] block: call __bio_free in bio_endio Shaohua Li
2017-06-15 18:17 ` [PATCH V3 11/12] blktrace: add an option to allow displying cgroup path Shaohua Li
2017-06-19 19:14 ` Tejun Heo [this message]
2017-06-15 18:17 ` [PATCH V3 12/12] block: use standard blktrace API to output cgroup info for debug notes Shaohua Li
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=20170619191446.GM12062@htj.duckdns.org \
--to=tj@kernel.org \
--cc=Kernel-team@fb.com \
--cc=axboe@fb.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=rostedt@goodmis.org \
--cc=shli@fb.com \
--cc=shli@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
all inboxes | Powered by JetHome®