From: Dean Marx <dmarx@iol.unh.edu>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [RFC PATCH] doc: clarify VLAN and QinQ stripping behaviour
Date: Wed, 16 Jul 2025 15:24:55 -0400 [thread overview]
Message-ID: <CABD7UXPtChUUOdz3gfiyKqY4Rn2_0F8Ck4O6ypq9woATD7hfCw@mail.gmail.com> (raw)
In-Reply-To: <aHd6x3kT053EvX2g@bricha3-mobl1.ger.corp.intel.com>
I've created a list of test cases which I'm planning on implementing
in future QinQ testing. After talking with Bruce about some Intel test
results earlier, I've got a solid idea of what the expected behaviors
are in five of these, but I'm unsure about the other three. If anyone
is able to provide some insight as to what they believe these expected
behaviors should be, please let me know as it would be immensely
helpful. Thanks!
Vlan Strip ON and QinQ Strip OFF:
1. Single VLAN:
Expected result: VLAN Stripped
2. Double VLAN:
Expected result: Should strip outer VLAN
3. Single 0x88a8 tag only:
Expected result: 0x88a8 tag stripped
4. Single VLAN + 1 0x88a8 tag:
Expected result: 0x88a8 tag stripped, inner VLAN untouched
Vlan Strip ON and QinQ Strip ON:
1. Single VLAN:
Expected result: VLAN stripped
2. Double VLAN:
Expected result: Unknown (Outer VLAN stripped?)
3. Single 0x88a8 tag only:
Expected result: Unknown (0x88a8 tag stripped?)
4. Single VLAN + 1 0x88a8 tag:
Expected result: Unknown (0x88a8 tag stripped and VLAN tag stripped?)
next prev parent reply other threads:[~2025-07-16 19:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 13:30 Bruce Richardson
2025-07-14 15:06 ` Stephen Hemminger
2025-07-14 15:11 ` Bruce Richardson
2025-07-14 16:33 ` Morten Brørup
2025-07-14 16:49 ` Bruce Richardson
2025-07-15 15:04 ` Morten Brørup
2025-07-15 16:20 ` Bruce Richardson
2025-07-14 20:09 ` Dean Marx
2025-07-14 21:41 ` Patrick Robb
2025-07-15 7:47 ` Bruce Richardson
2025-07-15 21:15 ` Patrick Robb
2025-07-16 10:11 ` Bruce Richardson
2025-07-16 19:24 ` Dean Marx [this message]
2025-07-16 19:46 ` Bruce Richardson
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=CABD7UXPtChUUOdz3gfiyKqY4Rn2_0F8Ck4O6ypq9woATD7hfCw@mail.gmail.com \
--to=dmarx@iol.unh.edu \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/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).