From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH] net/netvsc: fix definition of offload values
Date: Wed, 3 Jul 2019 08:50:01 -0700 [thread overview]
Message-ID: <20190703155001.23244-1-stephen@networkplumber.org> (raw)
The definition of ipsec and rsc offloads was incorrect.
Neither one of these is used by current driver, but the values
should be fixed now for future RSC support.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
drivers/net/netvsc/ndis.h | 26 +++++++++++++-------------
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/drivers/net/netvsc/ndis.h b/drivers/net/netvsc/ndis.h
index 2e7ca99b151f..d97a397a8604 100644
--- a/drivers/net/netvsc/ndis.h
+++ b/drivers/net/netvsc/ndis.h
@@ -262,17 +262,17 @@ struct ndis_lsov2_offload {
struct ndis_ipsecv2_offload {
uint32_t ndis_encap; /*NDIS_OFFLOAD_ENCAP_*/
- uint16_t ndis_ip6;
- uint16_t ndis_ip4opt;
- uint16_t ndis_ip6ext;
- uint16_t ndis_ah;
- uint16_t ndis_esp;
- uint16_t ndis_ah_esp;
- uint16_t ndis_xport;
- uint16_t ndis_tun;
- uint16_t ndis_xport_tun;
- uint16_t ndis_lso;
- uint16_t ndis_extseq;
+ uint8_t ndis_ip6;
+ uint8_t ndis_ip4opt;
+ uint8_t ndis_ip6ext;
+ uint8_t ndis_ah;
+ uint8_t ndis_esp;
+ uint8_t ndis_ah_esp;
+ uint8_t ndis_xport;
+ uint8_t ndis_tun;
+ uint8_t ndis_xport_tun;
+ uint8_t ndis_lso;
+ uint8_t ndis_extseq;
uint32_t ndis_udp_esp;
uint32_t ndis_auth;
uint32_t ndis_crypto;
@@ -280,8 +280,8 @@ struct ndis_ipsecv2_offload {
};
struct ndis_rsc_offload {
- uint16_t ndis_ip4;
- uint16_t ndis_ip6;
+ uint8_t ndis_ip4;
+ uint8_t ndis_ip6;
};
struct ndis_encap_offload {
--
2.20.1
next reply other threads:[~2019-07-03 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 15:50 Stephen Hemminger [this message]
2019-07-04 16: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=20190703155001.23244-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--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).