RE: [RFC v2] current devlink extension plan for NICs

2020-05-20 Thread Parav Pandit
> From: Jacob Keller > Sent: Wednesday, May 20, 2020 1:15 AM > > On 5/18/2020 10:17 PM, Parav Pandit wrote: > > Hi Jake, > > > > >> Ok. So in the smart NIC CPU, we'd see the primary PF and some child > >> PFs, and in the host system we'd see a "primary PF" that is the other > >> end of the asso

Re: [RFC v2] current devlink extension plan for NICs

2020-05-19 Thread Jacob Keller
On 5/18/2020 10:17 PM, Parav Pandit wrote: > Hi Jake, > >> Ok. So in the smart NIC CPU, we'd see the primary PF and some child PFs, >> and in the host system we'd see a "primary PF" that is the other end of the >> associated Child PF, and might be able to manage its own subswitch. >> >> Ok thi

Re: [RFC v2] current devlink extension plan for NICs

2020-05-18 Thread Jiri Pirko
Mon, May 18, 2020 at 11:05:45PM CEST, jacob.e.kel...@intel.com wrote: > > >On 5/17/2020 11:52 PM, Jiri Pirko wrote: >> Fri, May 15, 2020 at 11:36:19PM CEST, jacob.e.kel...@intel.com wrote: >>> >>> >>> On 5/15/2020 2:30 AM, Jiri Pirko wrote: Fri, May 15, 2020 at 01:52:54AM CEST, jacob.e.kel...@

RE: [RFC v2] current devlink extension plan for NICs

2020-05-18 Thread Parav Pandit
Hi Jake, > From: netdev-ow...@vger.kernel.org On > Behalf Of Jacob Keller > > > On 5/17/2020 11:52 PM, Jiri Pirko wrote: > > Fri, May 15, 2020 at 11:36:19PM CEST, jacob.e.kel...@intel.com wrote: > >> > >> > >> On 5/15/2020 2:30 AM, Jiri Pirko wrote: > >>> Fri, May 15, 2020 at 01:52:54AM CEST, j

Re: [RFC v2] current devlink extension plan for NICs

2020-05-18 Thread Jacob Keller
On 5/17/2020 11:52 PM, Jiri Pirko wrote: > Fri, May 15, 2020 at 11:36:19PM CEST, jacob.e.kel...@intel.com wrote: >> >> >> On 5/15/2020 2:30 AM, Jiri Pirko wrote: >>> Fri, May 15, 2020 at 01:52:54AM CEST, jacob.e.kel...@intel.com wrote: > $ devlink port add pci/.06.00.0/100 flavour pcisf

Re: [RFC v2] current devlink extension plan for NICs

2020-05-17 Thread Jiri Pirko
Fri, May 15, 2020 at 11:36:19PM CEST, jacob.e.kel...@intel.com wrote: > > >On 5/15/2020 2:30 AM, Jiri Pirko wrote: >> Fri, May 15, 2020 at 01:52:54AM CEST, jacob.e.kel...@intel.com wrote: $ devlink port add pci/.06.00.0/100 flavour pcisf pfnum 1 sfnum 10 >>> >>> Can you clarify what s

Re: [RFC v2] current devlink extension plan for NICs

2020-05-15 Thread Jacob Keller
On 5/15/2020 2:30 AM, Jiri Pirko wrote: > Fri, May 15, 2020 at 01:52:54AM CEST, jacob.e.kel...@intel.com wrote: >>> $ devlink port add pci/.06.00.0/100 flavour pcisf pfnum 1 sfnum 10 >>> >> >> Can you clarify what sfnum means here? and why is it different from the >> index? I get that the in

Re: [RFC v2] current devlink extension plan for NICs

2020-05-15 Thread Jiri Pirko
Fri, May 15, 2020 at 01:52:54AM CEST, jacob.e.kel...@intel.com wrote: > > >On 5/1/2020 2:14 AM, Jiri Pirko wrote: >> == >> || || >> || SF (subfunction) user cmdline

Re: [RFC v2] current devlink extension plan for NICs

2020-05-14 Thread Jacob Keller
On 5/1/2020 2:14 AM, Jiri Pirko wrote: > == > || || > || SF (subfunction) user cmdline API draft || > ||

Re: [oss-drivers] [RFC v2] current devlink extension plan for NICs

2020-05-13 Thread Jiri Pirko
Wed, May 13, 2020 at 03:00:09PM CEST, simon.hor...@netronome.com wrote: >On Fri, May 01, 2020 at 11:14:49AM +0200, Jiri Pirko wrote: >> Hi all. >> >> First, I would like to apologize for very long email. But I think it >> would be beneficial to the see the whole picture, where we are going. >> >>

Re: [oss-drivers] [RFC v2] current devlink extension plan for NICs

2020-05-13 Thread Simon Horman
On Fri, May 01, 2020 at 11:14:49AM +0200, Jiri Pirko wrote: > Hi all. > > First, I would like to apologize for very long email. But I think it > would be beneficial to the see the whole picture, where we are going. > > Currently we are working internally on several features with > need of extensi

Re: [RFC v2] current devlink extension plan for NICs

2020-05-11 Thread Jacob Keller
On 5/10/2020 7:45 AM, Jiri Pirko wrote: > Hello guys. > > Anyone has any opinion on the proposal? Or should I take it as a silent > agreement? :) I am still reading through this whole thing. I haven't given feedback yet because it is a lot to process. -Jake

Re: [RFC v2] current devlink extension plan for NICs

2020-05-10 Thread Jiri Pirko
Sun, May 10, 2020 at 06:30:59PM CEST, dave.t...@gmail.com wrote: >On Sun, May 10, 2020 at 7:46 AM Jiri Pirko wrote: >> >> Hello guys. >> >> Anyone has any opinion on the proposal? Or should I take it as a silent >> agreement? :) >> >> We would like to go ahead and start sending patchsets. > >I got

Re: [RFC v2] current devlink extension plan for NICs

2020-05-10 Thread Dave Taht
On Sun, May 10, 2020 at 7:46 AM Jiri Pirko wrote: > > Hello guys. > > Anyone has any opinion on the proposal? Or should I take it as a silent > agreement? :) > > We would like to go ahead and start sending patchsets. I gotta say that the whole thing makes my head really hurt, and while this conve

Re: [RFC v2] current devlink extension plan for NICs

2020-05-10 Thread Jiri Pirko
Hello guys. Anyone has any opinion on the proposal? Or should I take it as a silent agreement? :) We would like to go ahead and start sending patchsets. Thanks!

Re: [RFC v2] current devlink extension plan for NICs

2020-05-04 Thread Jiri Pirko
Mon, May 04, 2020 at 04:12:18AM CEST, sridhar.samudr...@intel.com wrote: > > >On 5/1/2020 2:14 AM, Jiri Pirko wrote: >> Hi all. >> >> First, I would like to apologize for very long email. But I think it >> would be beneficial to the see the whole picture, where we are going. >> >> Currently we ar

Re: [RFC v2] current devlink extension plan for NICs

2020-05-03 Thread Samudrala, Sridhar
On 5/1/2020 2:14 AM, Jiri Pirko wrote: Hi all. First, I would like to apologize for very long email. But I think it would be beneficial to the see the whole picture, where we are going. Currently we are working internally on several features with need of extension of the current devlink infr

[RFC v2] current devlink extension plan for NICs

2020-05-01 Thread Jiri Pirko
Hi all. First, I would like to apologize for very long email. But I think it would be beneficial to the see the whole picture, where we are going. Currently we are working internally on several features with need of extension of the current devlink infrastructure. I took a stab at putting it all