DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bernard Iremonger <bernard.iremonger@intel.com>
To: dev@dpdk.org, anatoly.burakov@intel.com
Cc: Bernard Iremonger <bernard.iremonger@intel.com>
Subject: [dpdk-dev] [PATCH] test: fix flow classify test
Date: Thu,  4 Jan 2018 10:39:46 +0000	[thread overview]
Message-ID: <1515062386-30337-1-git-send-email-bernard.iremonger@intel.com> (raw)

Remove the requirement to have a port bound to igb_uio in
order to run this test suite.

Fixes: 9c9befea4f57 ("test: add flow classify unit tests")
Reported by: Anatoly Burakov <anatoly.burakov@intel.com>

Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
---
 test/test/test_flow_classify.c | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/test/test/test_flow_classify.c b/test/test/test_flow_classify.c
index 9f331cd..a3bfd1d 100644
--- a/test/test/test_flow_classify.c
+++ b/test/test/test_flow_classify.c
@@ -610,18 +610,15 @@ struct flow_classifier_acl {
 	struct rte_table_acl_params table_acl_params;
 	struct rte_flow_classify_table_params cls_table_params;
 	struct rte_flow_classifier_params cls_params;
-	int socket_id;
 	int ret;
 	uint32_t size;
 
-	socket_id = rte_eth_dev_socket_id(0);
-
 	/* Memory allocation */
 	size = RTE_CACHE_LINE_ROUNDUP(sizeof(struct flow_classifier_acl));
 	cls = rte_zmalloc(NULL, size, RTE_CACHE_LINE_SIZE);
 
 	cls_params.name = "flow_classifier";
-	cls_params.socket_id = socket_id;
+	cls_params.socket_id = 0;
 	cls_params.type = RTE_FLOW_CLASSIFY_TABLE_TYPE_ACL;
 	cls->cls = rte_flow_classifier_create(&cls_params);
 
-- 
1.9.1

             reply	other threads:[~2018-01-04 10:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 10:39 Bernard Iremonger [this message]
2018-01-18  0:07 ` 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=1515062386-30337-1-git-send-email-bernard.iremonger@intel.com \
    --to=bernard.iremonger@intel.com \
    --cc=anatoly.burakov@intel.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).