-----Original Message-----
From: Jakub Kicinski <kuba@kernel.org>
Sent: Tuesday, December 6, 2022 9:24 AM
To: Leon Romanovsky <leon@kernel.org>
Cc: Veerasenareddy Burru <vburru@marvell.com>; David S. Miller
[off-list ref]; Eric Dumazet [off-list ref]; Paolo
Abeni [off-list ref]; netdev@vger.kernel.org; linux-
kernel@vger.kernel.org; Liron Himi [off-list ref]; Abhijit Ayarekar
[off-list ref]; Sathesh B Edara [off-list ref];
Satananda Burla [off-list ref]; linux-doc@vger.kernel.org
Subject: Re: [EXT] Re: [PATCH net-next v2 2/9] octeon_ep: poll for control
messages

On Tue, 6 Dec 2022 10:58:47 +0200 Leon Romanovsky wrote:

quoted

quoted

Polling for control messages every 100ms?  Sure.

You say "valid in netdev" so perhaps you can educate us where/why it
would not be?

It doesn't seem right to me that idle device burns CPU cycles, while
it supports interrupts. If it needs "listen to FW", it will be much
nicer to install interrupts immediately and don't wait for netdev.

No doubt, if there is an alternative we can push for it to be implemented. I
guess this being yet another "IPU" there could be possible workarounds in
FW? As always with IPUs - hard to tell :/

If there is no alternative - it is what it is.
It's up to customers to buy good HW.

That said, looking at what this set does - how are the VFs configured?
That's the showstopper for the series in my mind.

VFs are created by writing to sriov_numvfs.