From: Sujith Sankar <ssujith@cisco.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] enic: remove use of rte_fdir_filter for key_len
Date: Tue, 21 Apr 2015 11:21:28 +0530 [thread overview]
Message-ID: <1429595488-15992-1-git-send-email-ssujith@cisco.com> (raw)
This patch removes the use of rte_fdir_filter from enic_clsf.
This also takes care of modifying the version and copyright string.
Signed-off-by: Sujith Sankar <ssujith@cisco.com>
---
lib/librte_pmd_enic/enic.h | 4 ++--
lib/librte_pmd_enic/enic_clsf.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/lib/librte_pmd_enic/enic.h b/lib/librte_pmd_enic/enic.h
index 7528d7d..1417b0c 100644
--- a/lib/librte_pmd_enic/enic.h
+++ b/lib/librte_pmd_enic/enic.h
@@ -49,8 +49,8 @@
#define DRV_NAME "enic_pmd"
#define DRV_DESCRIPTION "Cisco VIC Ethernet NIC Poll-mode Driver"
-#define DRV_VERSION "1.0.0.4"
-#define DRV_COPYRIGHT "Copyright 2008-2014 Cisco Systems, Inc"
+#define DRV_VERSION "1.0.0.5"
+#define DRV_COPYRIGHT "Copyright 2008-2015 Cisco Systems, Inc"
#define ENIC_WQ_MAX 8
#define ENIC_RQ_MAX 8
diff --git a/lib/librte_pmd_enic/enic_clsf.c b/lib/librte_pmd_enic/enic_clsf.c
index 937723e..ca12d2d 100644
--- a/lib/librte_pmd_enic/enic_clsf.c
+++ b/lib/librte_pmd_enic/enic_clsf.c
@@ -246,7 +246,7 @@ int enic_clsf_init(struct enic *enic)
.name = "enicpmd_clsf_hash",
.entries = ENICPMD_CLSF_HASH_ENTRIES,
.bucket_entries = ENICPMD_CLSF_BUCKET_ENTRIES,
- .key_len = sizeof(struct rte_fdir_filter),
+ .key_len = RTE_HASH_KEY_LENGTH_MAX,
.hash_func = DEFAULT_HASH_FUNC,
.hash_func_init_val = 0,
.socket_id = SOCKET_0,
--
1.9.1
next reply other threads:[~2015-04-21 5:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 5:51 Sujith Sankar [this message]
2015-04-28 12:14 ` 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=1429595488-15992-1-git-send-email-ssujith@cisco.com \
--to=ssujith@cisco.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).