[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BYAPR18MB24234E1E6566B47FCA609BF8CC1B9@BYAPR18MB2423.namprd18.prod.outlook.com>
Date: Tue, 6 Dec 2022 21:19:26 +0000
From: Veerasenareddy Burru <vburru@...vell.com>
To: Jakub Kicinski <kuba@...nel.org>, Leon Romanovsky <leon@...nel.org>
CC: "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Liron Himi <lironh@...vell.com>,
Abhijit Ayarekar <aayarekar@...vell.com>,
Sathesh B Edara <sedara@...vell.com>,
Satananda Burla <sburla@...vell.com>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>
Subject: RE: [EXT] Re: [PATCH net-next v2 2/9] octeon_ep: poll for control
messages
> -----Original Message-----
> From: Jakub Kicinski <kuba@...nel.org>
> Sent: Tuesday, December 6, 2022 9:24 AM
> To: Leon Romanovsky <leon@...nel.org>
> Cc: Veerasenareddy Burru <vburru@...vell.com>; David S. Miller
> <davem@...emloft.net>; Eric Dumazet <edumazet@...gle.com>; Paolo
> Abeni <pabeni@...hat.com>; netdev@...r.kernel.org; linux-
> kernel@...r.kernel.org; Liron Himi <lironh@...vell.com>; Abhijit Ayarekar
> <aayarekar@...vell.com>; Sathesh B Edara <sedara@...vell.com>;
> Satananda Burla <sburla@...vell.com>; linux-doc@...r.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:
> > > 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.
Powered by blists - more mailing lists