Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: Sreeni (Sreenivasa) Busam (Stellus) <s.busam at stellus.com>
To: spdk@lists.01.org
Subject: [SPDK] Regarding collection of iostat information for application with SPDK driver.
Date: Mon, 06 Nov 2017 20:56:28 +0000	[thread overview]
Message-ID: <f84c1adb2f85482f9ab169e0c50dfefc@stellus.com> (raw)
In-Reply-To: CGME20171106205629uscas1p2c53192412c9dc2fa93aa22512ae91962@uscas1p2.samsung.com

[-- Attachment #1: Type: text/plain, Size: 867 bytes --]

Hello,

I am working on a tool to collect IO statistics like

1.      Read IOPS

2.      Write IOPS
and other metrics on a per process basis for SSD device and given namespace. The assumption is all the Read and Write I/O statistics and latency should be collected for a given process which may do I/O on one or more NVMe SSD devices based on a configuration file.
I am going through the lib/bdev code and trying to see where I can add the code to collect the statistics. I have spent only a few days looking into the SPDK code and new to the code.
Is this the right function, spdk_bdev_io_complete() for me to start looking into?
Please give any suggestions you have or what are the functions I should look into? Where should I investigate more to collect the I/O statistics?
I appreciate your ideas and any help in this regard.

Thanks a lot,
Sreeni

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 5072 bytes --]

             reply	other threads:[~2017-11-06 20:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-06 20:56 Sreeni Busam [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-07  1:22 [SPDK] Regarding collection of iostat information for application with SPDK driver Cao, Gang
2017-11-07  1:40 Sreeni Busam

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=f84c1adb2f85482f9ab169e0c50dfefc@stellus.com \
    --to=spdk@lists.01.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