DPDK patches and discussions
 help / color / mirror / Atom feed
From: Wei Zhao <wei.zhao1@intel.com>
To: dev@dpdk.org
Cc: wenzhuo.lu@intel.com, Wei Zhao <wei.zhao1@intel.com>
Subject: [dpdk-dev] [PATCH v2 2/2] net/e1000: fix flex filter length error
Date: Fri, 16 Jun 2017 13:04:24 +0800	[thread overview]
Message-ID: <1497589464-10183-2-git-send-email-wei.zhao1@intel.com> (raw)
In-Reply-To: <1497589464-10183-1-git-send-email-wei.zhao1@intel.com>

igb flex filter support a recognize any arbitrary
pattern within the first 128 bytes of the packet,
but the macro E1000_FLEX_FILTERS_MASK_SIZE define
only the first 64 byte.

Fixes: 231d43909a31 ("igb: migrate flex filter to new API")

Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
---
 drivers/net/e1000/e1000_ethdev.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/e1000/e1000_ethdev.h b/drivers/net/e1000/e1000_ethdev.h
index 9266540..85fd1a0 100644
--- a/drivers/net/e1000/e1000_ethdev.h
+++ b/drivers/net/e1000/e1000_ethdev.h
@@ -82,7 +82,7 @@
 #define E1000_MAX_FLEX_FILTER_DWDS \
 	(E1000_MAX_FLEX_FILTER_LEN / sizeof(uint32_t))
 #define E1000_FLEX_FILTERS_MASK_SIZE \
-	(E1000_MAX_FLEX_FILTER_DWDS / 4)
+	(E1000_MAX_FLEX_FILTER_DWDS / 2)
 #define E1000_FHFT_QUEUEING_LEN          0x0000007F
 #define E1000_FHFT_QUEUEING_QUEUE        0x00000700
 #define E1000_FHFT_QUEUEING_PRIO         0x00070000
-- 
2.7.4

  reply	other threads:[~2017-06-16  5:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16  3:15 [dpdk-dev] [PATCH 1/2] net/e1000: fix flex type filter Wei Zhao
2017-06-16  3:15 ` [dpdk-dev] [PATCH 2/2] net/e1000: fix flex filter length error Wei Zhao
2017-06-16  5:04 ` [dpdk-dev] [PATCH v2 1/2] net/e1000: fix flex type filter Wei Zhao
2017-06-16  5:04   ` Wei Zhao [this message]
2017-06-16 16:00   ` 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=1497589464-10183-2-git-send-email-wei.zhao1@intel.com \
    --to=wei.zhao1@intel.com \
    --cc=dev@dpdk.org \
    --cc=wenzhuo.lu@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).