From: Sergey Alekseev <sergey.alekseev@vdomresearch.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] ip_frag: fix hash key usage
Date: Wed, 21 Feb 2018 09:03:19 +0700 [thread overview]
Message-ID: <1519178599-3661-1-git-send-email-sergey.alekseev@vdomresearch.com> (raw)
---
lib/librte_ip_frag/ip_frag_internal.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/librte_ip_frag/ip_frag_internal.c b/lib/librte_ip_frag/ip_frag_internal.c
index 7397aa6..2cfa56b 100644
--- a/lib/librte_ip_frag/ip_frag_internal.c
+++ b/lib/librte_ip_frag/ip_frag_internal.c
@@ -61,7 +61,7 @@ ipv4_frag_hash(const struct ip_frag_key *key, uint32_t *v1, uint32_t *v2)
uint32_t v;
const uint32_t *p;
- p = (const uint32_t *)&key->src_dst;
+ p = (const uint32_t *) key->src_dst;
#ifdef RTE_ARCH_X86
v = rte_hash_crc_4byte(p[0], PRIME_VALUE);
@@ -82,7 +82,7 @@ ipv6_frag_hash(const struct ip_frag_key *key, uint32_t *v1, uint32_t *v2)
uint32_t v;
const uint32_t *p;
- p = (const uint32_t *) &key->src_dst;
+ p = (const uint32_t *) key->src_dst;
#ifdef RTE_ARCH_X86
v = rte_hash_crc_4byte(p[0], PRIME_VALUE);
--
2.7.4
next reply other threads:[~2018-02-21 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 2:03 Sergey Alekseev [this message]
2018-03-27 22:29 ` Thomas Monjalon
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=1519178599-3661-1-git-send-email-sergey.alekseev@vdomresearch.com \
--to=sergey.alekseev@vdomresearch.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).