DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ivan Malov <ivan.malov@oktetlabs.ru>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>,
	 John McNamara <john.mcnamara@intel.com>,
	 Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: Understanding RX_OFFLOAD_VLAN_EXTEND
Date: Mon, 31 Oct 2022 21:46:20 +0300 (MSK)	[thread overview]
Message-ID: <911e37b-7c27-5bbb-ca40-4b778d396fff@oktetlabs.ru> (raw)

Hi!

We have a hard time figuring out what the API contract of
RX_OFFLOAD_VLAN_EXTEND might be. The best educated guess
we can make is that the feature might have something to
do with identifying VLAN packets and extracting TCI
without stripping the tags from incoming packets.

Is this understanding correct?

You see, things aren't helped by the offload bit having
almost no commentary. Such could've shed light on its
meaning. Perhaps this gap in documentation should
be addressed somehow. Any opinions?

Thank you.

             reply	other threads:[~2022-10-31 18:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 18:46 Ivan Malov [this message]
2022-10-31 20:15 ` Ferruh Yigit
2022-10-31 21:56   ` Ivan Malov

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=911e37b-7c27-5bbb-ca40-4b778d396fff@oktetlabs.ru \
    --to=ivan.malov@oktetlabs.ru \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=thomas@monjalon.net \
    /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).