DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Tao, Zhe" <zhe.tao@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] i40e: add VEB switching support for i40e
Date: Fri, 19 Feb 2016 05:17:41 +0000	[thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F8DA85F6@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1453358984-20550-1-git-send-email-zhe.tao@intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Zhe Tao
> Sent: Thursday, January 21, 2016 2:50 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] i40e: add VEB switching support for i40e
> 
> VEB switching feature for i40e is used to enable the switching between the
>  VSIs connect to the virtual bridge. The old implementation is setting the
>  virtual bridge mode as VEPA which is port aggregation. Enable the switching
>  ability by setting the loop back mode for the specific VSIs which connect to PF
>  or VFs.

As I know, there is a known issue about the veb switch on older NVM version.
I would be better to add a NVM version verification, if version > xx.xx, then enable it?

Thanks
Jingjing

> Signed-off-by: Zhe Tao <zhe.tao@intel.com>
> ---
>  drivers/net/i40e/i40e_ethdev.c | 48 +++++++++++++++++++++++++++++++++++-------
>  1 file changed, 40 insertions(+), 8 deletions(-)
> 

  parent reply	other threads:[~2016-02-19  5:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21  6:49 Zhe Tao
2016-01-22 10:16 ` Thomas Monjalon
2016-01-25  6:22   ` Xu, Qian Q
2016-02-19  5:17 ` Wu, Jingjing [this message]
2016-02-23  3:48   ` Zhe Tao
2016-02-23  8:10 ` [dpdk-dev] [PATCH v2] " Zhe Tao
2016-02-25  0:42   ` Wu, Jingjing
2016-03-09  5:38   ` [dpdk-dev] [PATCH v3] " Zhe Tao
2016-03-09  6:02     ` Wu, Jingjing
2016-03-11 21:50       ` Bruce Richardson

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=9BB6961774997848B5B42BEC655768F8DA85F6@SHSMSX103.ccr.corp.intel.com \
    --to=jingjing.wu@intel.com \
    --cc=dev@dpdk.org \
    --cc=zhe.tao@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).