[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9BBC4E0CF881AA4299206E2E1412B62650491AAE@ORSMSX102.amr.corp.intel.com>
Date: Thu, 6 Jul 2017 15:26:42 +0000
From: "Wyborny, Carolyn" <carolyn.wyborny@...el.com>
To: Greg Rose <gvrose8192@...il.com>
CC: Stefan Assmann <sassmann@...nic.de>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>
Subject: RE: [Intel-wired-lan] [PATCH 1/2] i40e/i40evf: rename
vf_offload_flags to vf_cap_flags in struct virtchnl_vf_resource
> -----Original Message-----
> From: Greg Rose [mailto:gvrose8192@...il.com]
> Sent: Thursday, July 06, 2017 7:25 AM
> To: Wyborny, Carolyn <carolyn.wyborny@...el.com>
> Cc: Stefan Assmann <sassmann@...nic.de>; intel-wired-lan@...ts.osuosl.org;
> netdev@...r.kernel.org; davem@...emloft.net
> Subject: Re: [Intel-wired-lan] [PATCH 1/2] i40e/i40evf: rename
> vf_offload_flags to vf_cap_flags in struct virtchnl_vf_resource
>
> On Wed, Jul 5, 2017 at 10:15 PM, Wyborny, Carolyn
> <carolyn.wyborny@...el.com> wrote:
> >
> > > -----Original Message-----
> > > From: Intel-wired-lan [mailto:intel-wired-lan-bounces@...osl.org] On
> Behalf
> > > Of Stefan Assmann
> > > Sent: Thursday, June 29, 2017 6:12 AM
> > > To: intel-wired-lan@...ts.osuosl.org
> > > Cc: netdev@...r.kernel.org; davem@...emloft.net;
> sassmann@...nic.de
> > > Subject: [Intel-wired-lan] [PATCH 1/2] i40e/i40evf: rename
> vf_offload_flags to
> > > vf_cap_flags in struct virtchnl_vf_resource
> > >
> > > The current name of vf_offload_flags indicates that the bitmap is
> > > limited to offload related features. Make this more generic by renaming
> > > it to vf_cap_flags, which allows for other capabilities besides
> > > offloading to be added.
> > >
> > > Signed-off-by: Stefan Assmann <sassmann@...nic.de>
> > > ---
> >
> > Hello Stefan,
> >
> > Thanks for the patch series, but we believe the vf should be ignorant of its
> trusted status.
>
> Hi Carolyn,
>
> Might I ask why?
>
> Thanks,
>
> - Greg
Hello Greg,
The trusted status of the vf is something that pf manages, mostly for security reasons. The mailbox model of communication between them relies on the pf to have authority over the vf. In most things, the vf asks permission from the pf for changes in its configuration and this keeps the pf as the gatekeeper between trusted and regular vf's. However, the issue here is that changing the MAC address from within the vf does not go through the mailbox, so it cannot tell if the vf is trusted or not. We are working on a redesign of this feature to fix that instead of having the vf sort of know its trusted. If, for some reason, we are unable to redesign it that way we would reconsider this method instead.
Thanks,
Carolyn
Powered by blists - more mailing lists