From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f175.google.com (mail-wr0-f175.google.com [209.85.128.175]) by dpdk.org (Postfix) with ESMTP id 89CD2D018 for ; Tue, 28 Mar 2017 17:29:46 +0200 (CEST) Received: by mail-wr0-f175.google.com with SMTP id l43so108921520wre.1 for ; Tue, 28 Mar 2017 08:29:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=Z3m2Qz2mWmRH/Lvr2H9iZxEmh88Fqqk6p6Xrvhuu0iA=; b=fUpxtUZ4oh/Mz6orUz8pUedDrvdTcoFoCKc6Pbnq1/K5575JGnAVCYGRV7EfkIBxwG v3wyDB9T/RAMmwmxD3H/Pr4bOo4a6rF6BRiazHlCraIx/8JEuHE3xwg4sjb1FDg4edby SO/cvp2yg36tskmrctNTQoML7cDDJAdEide7Uex2Oa0lPyn0XvA/6oPq6z7/y0w0Oqa6 CoBY1MAHbaADJtNz8h578SAezrjfnqnbmr2dciUgMDmVa+NlQBc3s0gedbQ4H3kNeOik hS7IgFOtgXIdNnINV8cNfdMifcDgjKmEMzDW05f4yESVNbHmUP5pVDmQ/Up82XSupkUX eH7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=Z3m2Qz2mWmRH/Lvr2H9iZxEmh88Fqqk6p6Xrvhuu0iA=; b=IL9Lrfw5mJXek8DencdQUKwS2NCy3onFZFhphb8m1k5Cd0K7BzWcnwCtR/CNmwh8bC clOtjdN+XC73+V9nblRtCcCE3MRogxD/w30T2pfCINoa6v+hZyEbllxfvaI+9IwkuMnU RDj+t/bgJaeD9CbPgmnO+Apjyi6uJDxf2kjXwQrxdsOpRsPvWXB5yFR4HQAuXyZQW4YF 100LVKiBvH+UvIJJ9bwBfj2g3/F8SXRNJRf1+FQhOZhP/YsKSgCaBlEahcQGBBEUfNah OT9eHFcf1xpM3gy13xiqxaFtvkdoVPMfIgMJJ8w+2S3eII7A5/uCJJZK7jsm37aWxF9t MR6A== X-Gm-Message-State: AFeK/H0JgmmQxwhDoyZpRrT0/L2wDsUkQSUKSJ+9wp7zDro/cvhsZ4VrfLDWGfE9RX+2CKlz X-Received: by 10.223.150.88 with SMTP id c24mr14575897wra.202.1490714986284; Tue, 28 Mar 2017 08:29:46 -0700 (PDT) Received: from platinum (2a01cb0c03c651000226b0fffeed02fc.ipv6.abo.wanadoo.fr. [2a01:cb0c:3c6:5100:226:b0ff:feed:2fc]) by smtp.gmail.com with ESMTPSA id b199sm4083019wmb.13.2017.03.28.08.29.46 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 28 Mar 2017 08:29:46 -0700 (PDT) Date: Tue, 28 Mar 2017 17:29:43 +0200 From: Olivier Matz To: dev@dpdk.org, helin.zhang@intel.com, jingjing.wu@intel.com Message-ID: <20170328172943.7b157ef4@platinum> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [dpdk-dev] disable i40e vf vlan stripping X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Mar 2017 15:29:46 -0000 Hi i40e maintainers, I have the following configuration: - host runs with Linux pf i40e driver - guest runs with DPDK vf i40e driver I send a vlan packet from the host to the guest. On the guest, I start testpmd with --disable-hw-vlan-strip. When I receive the packet on the guest, it has the PKT_RX_VLAN_STRIPPED flag although I'm not asking for it. From what I understand, it is not possible to disable vlan stripping when using a Linux PF driver. Since the i40evf DPDK driver does not behave like what the application asks for, I think it should be fixed. What do you think about re-adding the vlan in software when dev_conf->rxmode.hw_vlan_strip == 0 ? The other alternative would be to forbid this configuration and return an error. Any opinion? Shall I send a patch? Thanks Olivier