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 this is making more sense now.
>>
>> I think I had imagined that was what subfuntions were. But really
>> subfunctions are a bit different, they're more similar to expanded VFs?
>>
>
> 1. Sub functions are more light weight than VFs because,
> 2. They share the same PCI device (BAR, IRQs) as that of PF/VF on which it is
> deployed.
> 3. Unlike VFs which are enabled/disabled in bulk, subfunctions are created,
> deployed in unit of 1.
>
> Since this RFC content is overwhelming, I expanded the SF plumbing details
> more in [1] in previous RFC version.
> You can replace 'devlink slice' with 'devlink port func' in [1].
>
> [1] https://marc.info/?l=linux-netdev&m=158555928517777&w=2
>
Thanks! Indeed, this makes things a lot more clear to me now.
Regards,
Jake
