From: Stephen Hemminger <stephen@networkplumber.org>
To: Tudor Cornea <tudor.cornea@gmail.com>
Cc: ferruh.yigit@intel.com, linville@tuxdriver.com,
andrew.rybchenko@oktetlabs.ru, thomas@monjalon.net,
jerinj@marvell.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] net/af_packet: reinsert the stripped vlan tag
Date: Fri, 24 Sep 2021 08:10:58 -0700 [thread overview]
Message-ID: <20210924081058.7f6f8a33@hermes.local> (raw)
In-Reply-To: <1632483885-84732-1-git-send-email-tudor.cornea@gmail.com>
On Fri, 24 Sep 2021 14:44:45 +0300
Tudor Cornea <tudor.cornea@gmail.com> wrote:
> +Features and Limitations of the af_packet PMD
> +---------------------------------------------
> +
> +Since the following commit, the Linux kernel strips the vlan tag
> +
> +.. code-block:: console
> +
> + commit bcc6d47903612c3861201cc3a866fb604f26b8b2
> + Author: Jiri Pirko <jpirko@xxxxxxxxxx>
> + Date: Thu Apr 7 19:48:33 2011 +0000
> +
> + net: vlan: make non-hw-accel rx path similar to hw-accel
> +
> +Running on such a kernel results in receiving untagged frames while using
> +the af_packet PMD. Fortunately, the stripped information is still available
> +for use in ``mbuf->vlan_tci``, and applications could check ``PKT_RX_VLAN_STRIPPED``.
> +
> +However, we currently don't have a way to describe offloads which can't be
> +disabled by PMDs, and this creates an inconsistency with the way applications
> +expect the PMD offloads to work, and requires them to be aware of which
> +underlying driver they use.
> +
> +Since release 21.11 the af_packet PMD will implement support for the
> +``DEV_RX_OFFLOAD_VLAN_STRIP`` offload, and users can control the desired vlan
> +stripping behavior.
> +
> +It's important to note that the default case will change. If previously,
> +the vlan tag was stripped, if the application now requires the same behavior,
> +it will need to configure ``rxmode.offloads`` with ``DEV_RX_OFFLOAD_VLAN_STRIP``.
> +
> +The PMD driver will re-insert the vlan tag transparently to the application
> +if the kernel strips it, as long as the ``DEV_RX_OFFLOAD_VLAN_STRIP`` is not
> +enabled.
This seems like the wrong place for this text.
It is not a new feature, it is a bug fix.
If you want to describe it as an enhancement, the text should be succinct and describe
the situation from user point of view. Something like:
Af_packet PMD now works with VLAN's on Linux
next prev parent reply other threads:[~2021-09-24 15:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 12:46 [dpdk-dev] [PATCH] net/af_packet: try to " Tudor Cornea
2021-08-31 15:31 ` Ferruh Yigit
2021-09-01 19:07 ` Tudor Cornea
2021-09-01 21:34 ` Stephen Hemminger
2021-09-02 10:49 ` Ferruh Yigit
2021-09-03 9:45 ` Tudor Cornea
2021-09-08 8:59 ` [dpdk-dev] [PATCH v2] net/af_packet: " Tudor Cornea
2021-09-20 15:40 ` Ferruh Yigit
2021-09-21 20:59 ` Tudor Cornea
2021-09-24 11:44 ` [dpdk-dev] [PATCH v3] " Tudor Cornea
2021-09-24 15:10 ` Stephen Hemminger [this message]
2021-09-29 14:13 ` Tudor Cornea
2021-09-29 14:08 ` [dpdk-dev] [PATCH v4] " Tudor Cornea
2021-09-30 8:14 ` Ferruh Yigit
2021-10-01 8:49 ` Tudor Cornea
2021-10-01 8:35 ` [dpdk-dev] [PATCH v5] " Tudor Cornea
2021-10-01 15:02 ` Stephen Hemminger
2021-10-06 9:42 ` Ferruh Yigit
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=20210924081058.7f6f8a33@hermes.local \
--to=stephen@networkplumber.org \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=linville@tuxdriver.com \
--cc=thomas@monjalon.net \
--cc=tudor.cornea@gmail.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).