On Mon, Oct 29, 2018 at 5:33 AM Sunil Kovvuri <sunil.kovvuri@xxxxxxxxx> wrote:
> On Sat, Oct 27, 2018 at 12:59 AM Arnd Bergmann <arnd@xxxxxxxx> wrote:
> > On Fri, Oct 26, 2018 at 6:33 PM Sunil Kovvuri <sunil.kovvuri@xxxxxxxxx> wrote:
> > > On Fri, Oct 26, 2018 at 9:56 PM Sunil Kovvuri <sunil.kovvuri@xxxxxxxxx> wrote:
> > Aside from this, there is the stuff that Andrew mentioned, which is the
> > most important: For anything that should /not/ be controlled by a
> > network interface for itself, you still need an administrative interface.
> > An example of this would be creating additional virtual functions,
> > assigning bandwidth allocation between them, or limiting the
> > data that can be transferred to and from a virtual function.
> >
> > Can you explain what your plan is to handle those?
> >
>
> This part is still under discussion, will get back on this.
Ok, no worries.
> Currently we are looking at a way for a administrator to limit the amount of
> resources that can be attached / allocated to a virtual function.
> Allowing administrator to limit data transfer or to give priorities etc is complex,
> we will look into that stuff later on.
Makes sense. When you get there, please have a look at how 'devlink' is
used in the mlx4/5, bnxt, liquidio, and nfp drivers. As I understand it,
that is what you need here, and you may be able to directly implement
the same interface that they have defined.
Arnd
