From: Jasvinder Singh <jasvinder.singh@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2] ip_pipeline: add check on nic's rxq and txq
Date: Tue, 1 Dec 2015 12:23:59 +0000 [thread overview]
Message-ID: <1448972639-13229-1-git-send-email-jasvinder.singh@intel.com> (raw)
In-Reply-To: <1441630435-14158-1-git-send-email-jasvinder.singh@intel.com>
This patch checks that rx queue and tx queue of each
link specified in ip pipeline configuration file are
used.
*v2
- fix checkpatch warnings
Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
---
examples/ip_pipeline/config_check.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/examples/ip_pipeline/config_check.c b/examples/ip_pipeline/config_check.c
index 8052bc4..1ff5763 100644
--- a/examples/ip_pipeline/config_check.c
+++ b/examples/ip_pipeline/config_check.c
@@ -98,6 +98,8 @@ check_links(struct app_params *app)
n_rxq = app_link_get_n_rxq(app, link);
+ APP_CHECK((n_rxq), "%s does not have any RXQ\n", link->name);
+
APP_CHECK((n_rxq == rxq_max + 1),
"%s RXQs are not contiguous (B)\n", link->name);
@@ -115,6 +117,8 @@ check_links(struct app_params *app)
/* Check that link RXQs are contiguous */
n_txq = app_link_get_n_txq(app, link);
+ APP_CHECK((n_txq), "%s does not have any TXQ\n", link->name);
+
for (i = 0; i < n_txq; i++) {
char name[APP_PARAM_NAME_SIZE];
int pos;
--
2.5.0
next prev parent reply other threads:[~2015-12-01 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 12:53 [dpdk-dev] [PATCH] " Jasvinder Singh
2015-09-07 13:29 ` Dumitrescu, Cristian
2015-12-01 12:23 ` Jasvinder Singh [this message]
2015-12-07 0:34 ` [dpdk-dev] [PATCH v2] " 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=1448972639-13229-1-git-send-email-jasvinder.singh@intel.com \
--to=jasvinder.singh@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).