From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com,
Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: [PATCH net 0/2] nfp: flower: fix matching and pushing vlan CFI bit
Date: Fri, 29 Mar 2019 19:04:42 -0700 [thread overview]
Message-ID: <20190330020444.3028-1-jakub.kicinski@netronome.com> (raw)
Hi,
This patch clears up some confusion around the meaning of bit 12
for FW messages related to VLAN and flower offload.
Pieter says:
It fixes issues with matching, pushing and popping vlan tags.
We replace the vlan CFI bit with a vlan present bit that
indicates the presence of a vlan tag. We also no longer set
the CFI when pushing vlan tags.
Pieter Jansen van Vuuren (2):
nfp: flower: replace CFI with vlan present
nfp: flower: remove vlan CFI bit from push vlan action
.../ethernet/netronome/nfp/flower/action.c | 3 +--
.../net/ethernet/netronome/nfp/flower/cmsg.h | 3 +--
.../net/ethernet/netronome/nfp/flower/match.c | 27 +++++++++----------
3 files changed, 15 insertions(+), 18 deletions(-)
--
2.21.0
next reply other threads:[~2019-03-30 2:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 2:04 Jakub Kicinski [this message]
2019-03-30 2:04 ` [PATCH net 1/2] nfp: flower: replace CFI with vlan present Jakub Kicinski
2019-03-30 2:04 ` [PATCH net 2/2] nfp: flower: remove vlan CFI bit from push vlan action Jakub Kicinski
2019-04-02 1:03 ` [PATCH net 0/2] nfp: flower: fix matching and pushing vlan CFI bit David Miller
2019-04-02 1:13 ` Jakub Kicinski
2019-04-02 1:31 ` David Miller
2019-04-02 2:36 ` [PATCH stable/5.0 " Jakub Kicinski
2019-04-02 2:36 ` [PATCH stable/5.0 1/2] nfp: flower: replace CFI with vlan present Jakub Kicinski
2019-04-02 2:36 ` [PATCH stable/5.0 2/2] nfp: flower: remove vlan CFI bit from push vlan action Jakub Kicinski
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=20190330020444.3028-1-jakub.kicinski@netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.