[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200714112421.06f20c5a@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Tue, 14 Jul 2020 11:24:21 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: "Wang, Haiyue" <haiyue.wang@...el.com>
Cc: "Nguyen, Anthony L" <anthony.l.nguyen@...el.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"nhorman@...hat.com" <nhorman@...hat.com>,
"sassmann@...hat.com" <sassmann@...hat.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
"Lu, Nannan" <nannan.lu@...el.com>,
"Bowers, AndrewX" <andrewx.bowers@...el.com>
Subject: Re: [net-next 1/5] ice: add the virtchnl handler for AdminQ command
On Tue, 14 Jul 2020 01:29:40 +0000 Wang, Haiyue wrote:
> > On Mon, 13 Jul 2020 10:43:16 -0700 Tony Nguyen wrote:
> > > From: Haiyue Wang <haiyue.wang@...el.com>
> > >
> > > The DCF (Device Config Function) is a named trust VF (always with ID 0,
> > > single entity per PF port) that can act as a sole controlling entity to
> > > exercise advance functionality such as adding switch rules for the rest
> > > of VFs.
> >
> > But why? This looks like a bifurcated driver to me.
>
> Yes, like bifurcated about flow control. This expands Intel AVF virtual channel
> commands, so that VF can talk to hardware indirectly, which is under control of
> PF. Then VF can set up the flow control for other VFs. This enrich current PF's
> Flow Director filter for PF itself only by ethtool.
Could you say a little more about the application and motivation for
this?
We are talking about a single control domain here, correct?
Powered by blists - more mailing lists