From: Tejun Heo <tj@kernel.org>
To: Muneendra <muneendra.kumar@broadcom.com>
Cc: jsmart2021@gmail.com, mkumar@redhat.com,
linux-scsi@vger.kernel.org, linux-nvme@lists.infradead.org,
linux-block@vger.kernel.org, emilne@redhat.com,
pbonzini@redhat.com
Subject: Re: [RFC v2 02/18] blkcg: Added a app identifier support for blkcg
Date: Mon, 19 Oct 2020 10:46:19 -0400 [thread overview]
Message-ID: <20201019144619.GC4418@mtj.thefacebook.com> (raw)
In-Reply-To: <1603093393-12875-3-git-send-email-muneendra.kumar@broadcom.com>
On Mon, Oct 19, 2020 at 01:12:57PM +0530, Muneendra wrote:
> This Patch added a unique application identifier i.e
> app_id knob to blkcg which allows identification of traffic
> sources at an individual cgroup based Applications
> (ex:virtual machine (VM))level in both host and
> fabric infrastructure.
>
> Provided the interface blkcg_get_app_identifier to
> grab the app identifier associated with a bio.
>
> Provided the interface blkcg_set_app_identifier to
> set the app identifier in a blkcgrp associated with cgroup id
>
> Signed-off-by: Muneendra <muneendra.kumar@broadcom.com>
>
> ---
> v2:
> renamed app_identifier to app_id
> removed the sysfs interface blkio.app_identifie under
> /sys/fs/cgroup/blkio
> Added a new interface blkcg_set_app_identifier
> ---
> block/blk-cgroup.c | 31 +++++++++++++++++++++++++++++++
> include/linux/blk-cgroup.h | 22 ++++++++++++++++++++++
> 2 files changed, 53 insertions(+)
>
> diff --git a/block/blk-cgroup.c b/block/blk-cgroup.c
> index 619a79b51068..672971521010 100644
> --- a/block/blk-cgroup.c
> +++ b/block/blk-cgroup.c
> @@ -546,6 +546,37 @@ static struct blkcg_gq *blkg_lookup_check(struct blkcg *blkcg,
> return __blkg_lookup(blkcg, q, true /* update_hint */);
> }
>
> +/*
> + * Sets the app_identifier field associted to blkcg
> + * @buf: application identifier
> + * @id: cgrp id
> + * @len: size of appid
> + */
> +int blkcg_set_app_identifier(char *buf, u64 id, size_t len)
Can you please use a name which is more specific?
> +{
> + struct cgroup *cgrp = NULL;
> + struct cgroup_subsys_state *css = NULL;
> + struct blkcg *blkcg = NULL;
> +
> + cgrp = cgroup_get_from_kernfs_id(id);
> + if (!cgrp)
> + return -ENOENT;
> +
> + css = cgroup_get_e_css(cgrp, &io_cgrp_subsys);
> + if (!css)
> + return -ENOENT;
> +
> + blkcg = css_to_blkcg(css);
> + if (!blkcg)
> + return -ENOENT;
> +
> + if (len > APPID_LEN)
> + return -EINVAL;
> + strlcpy(blkcg->app_id, buf, len);
Shouldn't the cgrp and css be put before exit?
> + return 0;
> +}
> +EXPORT_SYMBOL(blkcg_set_app_identifier);
> +
> /**
> * blkg_conf_prep - parse and prepare for per-blkg config update
> * @inputp: input string pointer
> diff --git a/include/linux/blk-cgroup.h b/include/linux/blk-cgroup.h
> index c8fc9792ac77..5bd3f9f397ac 100644
> --- a/include/linux/blk-cgroup.h
> +++ b/include/linux/blk-cgroup.h
> @@ -30,6 +30,8 @@
>
> /* Max limits for throttle policy */
> #define THROTL_IOPS_MAX UINT_MAX
> +#define APPID_LEN 128
> +
>
> #ifdef CONFIG_BLK_CGROUP
>
> @@ -55,6 +57,8 @@ struct blkcg {
> struct blkcg_policy_data *cpd[BLKCG_MAX_POLS];
>
> struct list_head all_blkcgs_node;
> + char app_id[APPID_LEN];
Please use a more specific name and gate them behind a CONFIG.
Thanks.
--
tejun
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-10-19 14:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 7:42 [RFC v2 00/18] blkcg:Support to track FC storage blk io traffic Muneendra
2020-10-19 7:42 ` [RFC v2 01/18] cgroup: Added cgroup_get_from_kernfs_id Muneendra
2020-10-19 14:43 ` Tejun Heo
2020-10-19 7:42 ` [RFC v2 02/18] blkcg: Added a app identifier support for blkcg Muneendra
2020-10-19 14:46 ` Tejun Heo [this message]
2020-10-19 15:13 ` Muneendra Kumar M
2020-10-19 15:19 ` Tejun Heo
2020-10-19 15:20 ` Muneendra Kumar M
2020-10-19 7:42 ` [RFC v2 03/18] nvme: Added a newsysfs attribute appid_store Muneendra
2020-10-19 7:42 ` [RFC v2 04/18] lpfc: vmid: Add the datastructure for supporting VMID in lpfc Muneendra
2020-10-19 7:43 ` [RFC v2 05/18] lpfc: vmid: API to check if VMID is enabled Muneendra
2020-10-19 7:43 ` [RFC v2 06/18] lpfc: vmid: Supplementary data structures for vmid Muneendra
2020-10-19 7:43 ` [RFC v2 07/18] lpfc: vmid: Forward declarations for APIs Muneendra
2020-10-19 7:43 ` [RFC v2 08/18] lpfc: vmid: Add support for vmid in mailbox command Muneendra
2020-10-19 7:43 ` [RFC v2 09/18] lpfc: vmid: VMID params initialization Muneendra
2020-10-19 7:43 ` [RFC v2 10/18] lpfc: vmid: vmid resource allocation Muneendra
2020-10-19 7:43 ` [RFC v2 11/18] lpfc: vmid: cleanup vmid resources Muneendra
2020-10-19 7:43 ` [RFC v2 12/18] lpfc: vmid: Implements ELS commands for appid patch Muneendra
2020-10-19 7:43 ` [RFC v2 13/18] lpfc: vmid: Functions to manage vmids Muneendra
2020-10-19 7:43 ` [RFC v2 14/18] lpfc: vmid: Implements CT commands for appid Muneendra
2020-10-19 7:43 ` [RFC v2 15/18] lpfc: vmid: Appends the vmid in the wqe before sending request Muneendra
2020-10-19 7:43 ` [RFC v2 16/18] lpfc: vmid: Timeout implementation for vmid Muneendra
2020-10-19 7:43 ` [RFC v2 17/18] lpfc: vmid: Adding qfpa and vmid timeout check in worker thread Muneendra
2020-10-19 7:43 ` [RFC v2 18/18] lpfc: vmid: Introducing vmid in io path Muneendra
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=20201019144619.GC4418@mtj.thefacebook.com \
--to=tj@kernel.org \
--cc=emilne@redhat.com \
--cc=jsmart2021@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mkumar@redhat.com \
--cc=muneendra.kumar@broadcom.com \
--cc=pbonzini@redhat.com \
/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).