From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ferruh.yigit@intel.com>
Received: from mga05.intel.com (mga05.intel.com [192.55.52.43])
 by dpdk.org (Postfix) with ESMTP id CEE3B1B254
 for <dev@dpdk.org>; Fri, 10 Nov 2017 02:19:54 +0100 (CET)
Received: from fmsmga003.fm.intel.com ([10.253.24.29])
 by fmsmga105.fm.intel.com with ESMTP; 09 Nov 2017 17:19:53 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.44,371,1505804400"; 
   d="scan'208";a="363560"
Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.241.224.59])
 ([10.241.224.59])
 by FMSMGA003.fm.intel.com with ESMTP; 09 Nov 2017 17:19:53 -0800
To: Chillance Zen <chillancezen@gmail.com>, dev@dpdk.org,
 Jie Zheng <jzheng.bjtu@gmail.com>
References: <CAKQ7xkUafr_A8Xh6y7jJxFS07s7gUoUhrF8cuihG3LNHYqHcvQ@mail.gmail.com>
From: Ferruh Yigit <ferruh.yigit@intel.com>
Message-ID: <854bf65c-be7d-c783-5cf3-1790f3762567@intel.com>
Date: Thu, 9 Nov 2017 17:19:53 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CAKQ7xkUafr_A8Xh6y7jJxFS07s7gUoUhrF8cuihG3LNHYqHcvQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [dpdk-dev] vlan intertion offload does not take effect in 17.08
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Nov 2017 01:19:55 -0000

On 11/9/2017 2:27 AM, Chillance Zen wrote:
> hi,all
> I write this code when processing a packet try to utilize VLAN offload(the
> nic does support that offlaod because I verify it in its dev_info)
> 
> m->vlan_tci=222;
> m->ol_flags=PKT_TX_VLAN_PKT;
> 
> the packets out of that interface does not contain any vlan tag.
> 
> does anybody know what's happening or anything has changed since 17.08?

In Rx path, the meaning of the PKT_RX_VLAN changed in this release [1], but Tx
path should be same.

[1]
Commit: 380a7aab1ae2 ("mbuf: rename deprecated VLAN flags")

> 
> Regards
>