There are 3 RPC calls that are used by spdk_top, which provide stats:
thread_get_stats
thread_get_pollers
framework_get_reactors
They provide stats on pollers and threads associated with poll groups as well. More
detailed stats regarding poll groups are planned to be implemented.
Regards,
Maciek
-----Original Message-----
From: Or Gerlitz <gerlitz.or(a)gmail.com>
Sent: Sunday, September 6, 2020 12:59 PM
To: Harris, James R <james.r.harris(a)intel.com>
Cc: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] Re: spdk_top enhancements
On Tue, Sep 1, 2020 at 5:23 PM Harris, James R <james.r.harris(a)intel.com> wrote:
ο»ΏOn 9/1/20, 5:50 AM, "Or Gerlitz"
<gerlitz.or(a)gmail.com> wrote:
There is no intention to have spdk_top expose data via RPC. Scripts
can submit RPCs directly to the application under test to gather information and then
post-process it any way it wants.
got it, is there some RPC to get initiator drivers (e.g nvme
pci/rdma/tcp) idle/busy cycles or
the initiator sw architecture (poll groups and such) is not supported for that matter?
_______________________________________________
SPDK mailing list -- spdk(a)lists.01.org
To unsubscribe send an email to spdk-leave(a)lists.01.org