mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shaohua Li <shli@kernel.org>
To: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Cc: tj@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: [PATCH V3 07/12] cgroup: export fhandle info for a cgroup
Date: Thu, 15 Jun 2017 11:17:15 -0700	[thread overview]
Message-ID: <7687dd4e9f2e2e7fd3797cd76434d0df55c7d17b.1497549993.git.shli@fb.com> (raw)
In-Reply-To: <cover.1497549993.git.shli@fb.com>
In-Reply-To: <cover.1497549993.git.shli@fb.com>

From: Shaohua Li <shli@fb.com>

Add an API to export cgroup fhandle info. We don't export a full 'struct
file_handle', there are unrequired info. Sepcifically, cgroup is always
a directory, so we don't need a 'FILEID_INO32_GEN_PARENT' type fhandle,
we only need export the inode number and generation number just like
what generic_fh_to_parent does. And we can avoid the overhead of getting
an inode too, since kernfs_node has all the info required.

Signed-off-by: Shaohua Li <shli@fb.com>
---
 include/linux/cgroup.h | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/include/linux/cgroup.h b/include/linux/cgroup.h
index 30c6877..5ebe89f 100644
--- a/include/linux/cgroup.h
+++ b/include/linux/cgroup.h
@@ -609,6 +609,10 @@ static inline void cgroup_kthread_ready(void)
 	current->no_cgroup_migration = 0;
 }
 
+static inline struct kernfs_node_id *cgroup_get_node_id(struct cgroup *cgrp)
+{
+	return &cgrp->kn->id;
+}
 #else /* !CONFIG_CGROUPS */
 
 struct cgroup_subsys_state;
@@ -631,6 +635,10 @@ static inline int cgroup_init_early(void) { return 0; }
 static inline int cgroup_init(void) { return 0; }
 static inline void cgroup_init_kthreadd(void) {}
 static inline void cgroup_kthread_ready(void) {}
+static inline struct kernfs_node_id *cgroup_get_node_id(struct cgroup *cgrp)
+{
+	return NULL;
+}
 
 static inline bool task_under_cgroup_hierarchy(struct task_struct *task,
 					       struct cgroup *ancestor)
-- 
2.9.3

  parent reply	other threads:[~2017-06-15 18:17 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 ` Shaohua Li [this message]
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
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=7687dd4e9f2e2e7fd3797cd76434d0df55c7d17b.1497549993.git.shli@fb.com \
    --to=shli@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=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

all inboxes | Powered by JetHome®