From: Ming Lei <tom.leiming@gmail.com>
To: Muneendra Kumar M <muneendra.kumar@broadcom.com>
Cc: Tejun Heo <tj@kernel.org>, Hannes Reinecke <hare@suse.de>,
James Smart <james.smart@broadcom.com>,
Daniel Wagner <dwagner@suse.de>,
linux-block <linux-block@vger.kernel.org>,
Linux SCSI List <linux-scsi@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Ewan Milne <emilne@redhat.com>,
mkumar@redhat.com
Subject: Re: [RFC 01/16] blkcg:Introduce blkio.app_identifier knob to blkio controller
Date: Thu, 6 Aug 2020 10:22:13 +0800 [thread overview]
Message-ID: <CACVXFVOYc9KAaLsQ1kPa_bW_MsUgcxhqec45f24pB62=r-KXPg@mail.gmail.com> (raw)
In-Reply-To: <c40bc34840566366177a84b0d8b7ae90@mail.gmail.com>
On Thu, Aug 6, 2020 at 1:15 AM Muneendra Kumar M
<muneendra.kumar@broadcom.com> wrote:
>
> Hi Tejun,
> Our main requirement is to track the bio requests coming from different VM
> /container applications at the blk device layer(fc,scsi,nvme).
> By the time IO request comes to the blk device layer, the context of the
> application is lost and we can't track whose IO this belongs.
>
> In our approach we used the block cgroup to achieve this requirement.
> Since Requests also have access to the block cgroup via
> bio->bi_blkg->blkcg, and from there we can get the VM UUID.
> Therefore we added the VM UUID(app_identifier) to struct blkcg and define
> the accessors in blkcg_files and blkcg_legacy_files.
>
> Could you please let me know is there any another way where we can get the
> VM UUID info with the help of blkcg.
As Tejun suggested, the mapping between bio->bi_blkg->blkcg and the
unique ID could be built in usage scope, such as fabric
infrastructure, something like
xarray/hash may help to do that without much difficulty.
Thanks,
Ming
next prev parent reply other threads:[~2020-08-06 2:22 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 2:13 [RFC 00/16] Application specific identification support Muneendra
2020-08-04 2:13 ` [RFC 01/16] blkcg:Introduce blkio.app_identifier knob to blkio controller Muneendra
2020-08-04 11:31 ` Daniel Wagner
2020-08-04 14:21 ` Tejun Heo
2020-08-05 0:39 ` James Smart
2020-08-05 3:59 ` Ming Lei
2020-08-05 6:33 ` Hannes Reinecke
2020-08-05 14:39 ` Tejun Heo
2020-08-05 17:14 ` Muneendra Kumar M
2020-08-05 17:31 ` Tejun Heo
2020-08-06 2:22 ` Ming Lei [this message]
2020-08-06 12:31 ` Muneendra Kumar M
2020-08-06 13:41 ` Paolo Bonzini
2020-08-04 2:13 ` [RFC 02/16] lpfc: vmid: Add the datastructure for supporting VMID in lpfc Muneendra
2020-08-04 2:13 ` [RFC 03/16] lpfc: vmid: API to check if VMID is enabled Muneendra
2020-08-04 2:13 ` [RFC 04/16] lpfc: vmid: Supplementary data structures for vmid Muneendra
2020-08-04 2:13 ` [RFC 05/16] lpfc: vmid: Forward declarations for APIs Muneendra
2020-08-04 2:13 ` [RFC 06/16] lpfc: vmid: Add support for vmid in mailbox command Muneendra
2020-08-04 2:13 ` [RFC 07/16] lpfc: vmid: VMID params initialization Muneendra
2020-08-04 2:13 ` [RFC 08/16] lpfc: vmid: vmid resource allocation Muneendra
2020-08-04 2:13 ` [RFC 09/16] lpfc: vmid: cleanup vmid resources Muneendra
2020-08-04 2:13 ` [RFC 10/16] lpfc: vmid: Implements ELS commands for appid patch Muneendra
2020-08-04 2:13 ` [RFC 11/16] lpfc: vmid: Functions to manage vmids Muneendra
2020-08-04 2:13 ` [RFC 12/16] lpfc: vmid: Implements CT commands for appid Muneendra
2020-08-04 2:13 ` [RFC 13/16] lpfc: vmid: Appends the vmid in the wqe before sending request Muneendra
2020-08-04 2:13 ` [RFC 14/16] lpfc: vmid: Timeout implementation for vmid Muneendra
2020-08-04 2:13 ` [RFC 15/16] lpfc: vmid: Adding qfpa and vmid timeout check in worker thread Muneendra
2020-08-04 2:13 ` [RFC 16/16] lpfc: vmid: Introducing vmid in io path Muneendra
2020-08-05 7:16 ` Hannes Reinecke
2020-08-05 23:38 ` James Smart
2020-08-06 12:34 ` Muneendra Kumar M
2020-08-06 14:32 ` Paolo Bonzini
2020-08-06 16:26 ` Muneendra Kumar M
2020-08-06 18:41 ` Paolo Bonzini
2020-08-07 11:24 ` Muneendra Kumar M
2020-08-07 11:38 ` Paolo Bonzini
2020-08-07 12:17 ` Muneendra Kumar M
2020-08-10 9:03 ` Paolo Bonzini
2020-08-10 12:13 ` Muneendra Kumar M
2020-08-12 7:54 ` Paolo Bonzini
2020-08-12 12:16 ` Muneendra Kumar M
2020-08-07 12:32 ` Muneendra Kumar M
2020-08-11 23:48 ` James Smart
2020-08-06 14:41 ` Tejun Heo
2020-08-06 14:46 ` Paolo Bonzini
2020-08-06 14:48 ` Tejun Heo
2020-08-06 14:54 ` Paolo Bonzini
2020-08-06 14:59 ` Tejun Heo
2020-08-06 18:39 ` Paolo Bonzini
2020-08-06 18:49 ` Tejun Heo
2020-08-06 19:20 ` Paolo Bonzini
2020-08-06 19:32 ` Tejun Heo
2020-08-07 12:14 ` Paolo Bonzini
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='CACVXFVOYc9KAaLsQ1kPa_bW_MsUgcxhqec45f24pB62=r-KXPg@mail.gmail.com' \
--to=tom.leiming@gmail.com \
--cc=dwagner@suse.de \
--cc=emilne@redhat.com \
--cc=hare@suse.de \
--cc=james.smart@broadcom.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mkumar@redhat.com \
--cc=muneendra.kumar@broadcom.com \
--cc=pbonzini@redhat.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;
as well as URLs for NNTP newsgroup(s).