From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [iproute2 PATCH] iplink: Support VF Trust
Date: Mon, 12 Oct 2015 11:59:30 -0700 [thread overview]
Message-ID: <1444676370.2781.15.camel@intel.com> (raw)
In-Reply-To: <20151012095423.4feabde1@urahara>
On Mon, 2015-10-12 at 09:54 -0700, Stephen Hemminger wrote:
> On Wed, 7 Oct 2015 10:06:32 +0000
> Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com> wrote:
>
> > From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
> >
> > Add IFLA_VF_TRUST message to trust the VF.
> > PF can accept some privileged operation from the trusted VF.
> > For example, ixgbe PF doesn't allow to enable VF promiscuous mode
> until
> > the VF is trusted because it may hurt performance.
> >
> > To trust VF.
> > # ip link set dev eth0 vf 1 trust on
> >
> > To untrust VF.
> > # ip link set dev eth0 vf 1 trust off
> >
> > Signed-off-by: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
>
> I am waiting until this is accepted into kernel before merging it
> into iproute2.
Yeah, I figured. I had him resend it since our validation team did not
have these changes available to test Hiroshi's latest set of
driver/core changes.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20151012/01b9a561/attachment.asc>
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
Cc: "Rose, Gregory V" <gregory.v.rose@intel.com>,
Or Gerlitz <gerlitz.or@gmail.com>,
Alexander Duyck <alexander.duyck@gmail.com>,
"Skidmore, Donald C" <donald.c.skidmore@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"nhorman@redhat.com" <nhorman@redhat.com>,
"jogreene@redhat.com" <jogreene@redhat.com>,
Linux Netdev List <netdev@vger.kernel.org>,
"Choi, Sy Jong" <sy.jong.choi@intel.com>,
Rony Efraim <ronye@mellanox.com>,
Edward Cree <ecree@solarflare.com>,
David Miller <davem@davemloft.net>,
"sassmann@redhat.com" <sassmann@redhat.com>
Subject: Re: [iproute2 PATCH] iplink: Support VF Trust
Date: Mon, 12 Oct 2015 11:59:30 -0700 [thread overview]
Message-ID: <1444676370.2781.15.camel@intel.com> (raw)
In-Reply-To: <20151012095423.4feabde1@urahara>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
On Mon, 2015-10-12 at 09:54 -0700, Stephen Hemminger wrote:
> On Wed, 7 Oct 2015 10:06:32 +0000
> Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com> wrote:
>
> > From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
> >
> > Add IFLA_VF_TRUST message to trust the VF.
> > PF can accept some privileged operation from the trusted VF.
> > For example, ixgbe PF doesn't allow to enable VF promiscuous mode
> until
> > the VF is trusted because it may hurt performance.
> >
> > To trust VF.
> > # ip link set dev eth0 vf 1 trust on
> >
> > To untrust VF.
> > # ip link set dev eth0 vf 1 trust off
> >
> > Signed-off-by: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
>
> I am waiting until this is accepted into kernel before merging it
> into iproute2.
Yeah, I figured. I had him resend it since our validation team did not
have these changes available to test Hiroshi's latest set of
driver/core changes.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-10-12 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 10:06 [Intel-wired-lan] [iproute2 PATCH] iplink: Support VF Trust Hiroshi Shimamoto
2015-10-07 10:06 ` Hiroshi Shimamoto
2015-10-12 16:54 ` [Intel-wired-lan] " Stephen Hemminger
2015-10-12 16:54 ` Stephen Hemminger
2015-10-12 18:59 ` Jeff Kirsher [this message]
2015-10-12 18:59 ` Jeff Kirsher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1444676370.2781.15.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=intel-wired-lan@osuosl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.