Re: [RFC] PCI: Allow sysfs control over totalvfs

> >> One of the motivations for introducing devlink interface was to allow > >> user to pass some kind of well defined option parameters or as you call > >> it hints to driver module. That would allow to replace module options > >> and introduce similar possibility to pre-configure hardware on

Re: [RFC] PCI: Allow sysfs control over totalvfs

Tue, Sep 20, 2016 at 10:27:24PM CEST, yuval.mi...@cavium.com wrote: >> >Some of the HW capable of SRIOV has resource limitations, where the >> >PF and VFs resources are drawn from a common pool. >> >In some cases, these limitations have to be considered early during >> >chip initialization and can

Re: [RFC] PCI: Allow sysfs control over totalvfs

On Tue, Sep 20, 2016 at 8:49 AM, Yuval Mintz wrote: > [Sorry in advance if this was already discussed in the past] > > Some of the HW capable of SRIOV has resource limitations, where the > PF and VFs resources are drawn from a common pool. > In some cases, these

Re: [RFC] PCI: Allow sysfs control over totalvfs

> >Some of the HW capable of SRIOV has resource limitations, where the > >PF and VFs resources are drawn from a common pool. > >In some cases, these limitations have to be considered early during > >chip initialization and can only be changed by tearing down the > >configuration and

Re: [RFC] PCI: Allow sysfs control over totalvfs

Tue, Sep 20, 2016 at 05:49:48PM CEST, yuval.mi...@qlogic.com wrote: >[Sorry in advance if this was already discussed in the past] > >Some of the HW capable of SRIOV has resource limitations, where the >PF and VFs resources are drawn from a common pool. >In some cases, these limitations have to be

[RFC] PCI: Allow sysfs control over totalvfs

[Sorry in advance if this was already discussed in the past] Some of the HW capable of SRIOV has resource limitations, where the PF and VFs resources are drawn from a common pool. In some cases, these limitations have to be considered early during chip initialization and can only be changed by