From: Leyi Rong <leyi.rong@intel.com>
To: qi.z.zhang@intel.com
Cc: dev@dpdk.org, Leyi Rong <leyi.rong@intel.com>
Subject: [dpdk-dev] [PATCH v2 0/3] update ice code that were not working correctly
Date: Mon, 1 Jul 2019 13:04:47 +0800 [thread overview]
Message-ID: <20190701050450.43330-1-leyi.rong@intel.com> (raw)
In-Reply-To: <20190626023025.7039-1-leyi.rong@intel.com>
Main changes:
1. Add support for IPv6 based switch filters
2. Add support for ethertype switch filters
3. fix inner L2 offset in GRE dummy packet
Leyi Rong (3):
net/ice/base: add support for IPv6 based switch filters
net/ice/base: add support for ethertype switch filters
net/ice/base: fix inner L2 offset in GRE dummy packet
drivers/net/ice/base/ice_protocol_type.h | 22 +++--
drivers/net/ice/base/ice_switch.c | 119 +++++++++++++++++++++--
2 files changed, 124 insertions(+), 17 deletions(-)
--
2.17.1
next prev parent reply other threads:[~2019-07-01 5:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 2:30 [dpdk-dev] [PATCH 0/3] some update on CVL shared code Leyi Rong
2019-06-26 2:30 ` [dpdk-dev] [PATCH 1/3] net/ice/base: add support for IPv6 based switch filters Leyi Rong
2019-06-26 2:30 ` [dpdk-dev] [PATCH 2/3] net/ice/base: add support for ethertype " Leyi Rong
2019-06-26 3:00 ` Zhao1, Wei
2019-06-26 2:30 ` [dpdk-dev] [PATCH 3/3] net/ice/base: fix inner L2 offset in GRE dummy packet Leyi Rong
2019-06-26 5:29 ` [dpdk-dev] [PATCH 0/3] some update on CVL shared code Yang, Qiming
2019-06-26 9:36 ` Zhao1, Wei
2019-06-27 2:05 ` Yang, Qiming
2019-07-01 5:04 ` Leyi Rong [this message]
2019-07-01 5:04 ` [dpdk-dev] [PATCH v2 1/3] net/ice/base: add support for IPv6 based switch filters Leyi Rong
2019-07-01 5:04 ` [dpdk-dev] [PATCH v2 2/3] net/ice/base: add support for ethertype " Leyi Rong
2019-07-01 5:04 ` [dpdk-dev] [PATCH v2 3/3] net/ice/base: fix inner L2 offset in GRE dummy packet Leyi Rong
2019-07-01 5:46 ` [dpdk-dev] [PATCH v2 0/3] update ice code that were not working correctly Zhang, Qi Z
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=20190701050450.43330-1-leyi.rong@intel.com \
--to=leyi.rong@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.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).