DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Chen, Jing D" <jing.d.chen@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
	Shaham Fridenberg <ShahamF@Radware.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] fm10k pmd limitations
Date: Thu, 12 Jan 2017 13:30:35 +0000	[thread overview]
Message-ID: <4341B239C0EFF9468EE453F9E9F4604D3C5DA797@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <c0c1f059-5a7a-de91-7f9a-fc085503e639@intel.com>



> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Thursday, January 12, 2017 7:57 PM
> To: Shaham Fridenberg <ShahamF@Radware.com>; dev@dpdk.org
> Cc: Chen, Jing D <jing.d.chen@intel.com>
> Subject: Re: [dpdk-dev] fm10k pmd limitations
> 
> On 12/13/2016 1:49 PM, Shaham Fridenberg wrote:
> > Hey guys,
> >
> > I'm using dpdk 16.4 and fm10k card. According to the code, there's no
> support for disabling vlan stripping and VLAN QinQ in pmd fm10k.
> > Does anybody know why? If there's any way to work-around it, or when is a
> behavior change expected?

Yes, HW will always strip it and driver will copy it into 
(struct rte_mbuf *)mbuf->vlan_tci. 

> > I need my VF to receive the packets with the  VLAN headers.

VF can read from rte_mbuf.

> > Even if it's possible to change this configurations through the linux kernel
> fm10k driver?
> >
> > Thanks!
> >
> 
> CC fm10k maintainer: Jing Chen <jing.d.chen@intel.com>

      reply	other threads:[~2017-01-12 13:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13 13:49 Shaham Fridenberg
2017-01-12 11:56 ` Ferruh Yigit
2017-01-12 13:30   ` Chen, Jing D [this message]

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=4341B239C0EFF9468EE453F9E9F4604D3C5DA797@shsmsx102.ccr.corp.intel.com \
    --to=jing.d.chen@intel.com \
    --cc=ShahamF@Radware.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@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).