[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200811073144-mutt-send-email-mst@kernel.org>
Date: Tue, 11 Aug 2020 07:33:26 -0400
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Eli Cohen <elic@...dia.com>
Cc: Jason Wang <jasowang@...hat.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"eli@...lanox.com" <eli@...lanox.com>,
"lulu@...hat.com" <lulu@...hat.com>,
Majd Dibbiny <majd@...dia.com>,
Maor Dickman <maord@...dia.com>,
Shahaf Shuler <shahafs@...lanox.com>
Subject: Re: VDPA Debug/Statistics
On Tue, Aug 11, 2020 at 11:26:20AM +0000, Eli Cohen wrote:
> Hi All
>
> Currently, the only statistics we get for a VDPA instance comes from the virtio_net device instance. Since VDPA involves hardware acceleration, there can be quite a lot of information that can be fetched from the underlying device. Currently there is no generic method to fetch this information.
>
> One way of doing this can be to create a the host, a net device for each VDPA instance, and use it to get this information or do some configuration. Ethtool can be used in such a case
>
> I would like to hear what you think about this or maybe you have some other ideas to address this topic.
>
> Thanks,
> Eli
Something I'm not sure I understand is how are vdpa instances created
on mellanox cards? There's a devlink command for that, is that right?
Can that be extended for stats?
--
MST
Powered by blists - more mailing lists