From: Vipin Varghese <vipin.varghese@amd.com>
To: <dev@dpdk.org>, <fengchengwen@huawei.com>
Cc: <ferruh.yigit@amd.com>, <neerav.parikh@amd.com>
Subject: [PATCH] app/dma-perf: calrify incorrect NUMA config
Date: Wed, 6 Mar 2024 20:32:04 +0530 [thread overview]
Message-ID: <20240306150204.1375-1-vipin.varghese@amd.com> (raw)
Current commit decalres either `source or destination numa is greater
than acture numa` as cause of error. Rephrase as `Source or Destination`
is incorrect numa by checking which is greater than available numa.
Signed-off-by: Vipin Varghese <vipin.varghese@amd.com>
---
app/test-dma-perf/benchmark.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/app/test-dma-perf/benchmark.c b/app/test-dma-perf/benchmark.c
index 9b1f58c78c..5634ff8bf8 100644
--- a/app/test-dma-perf/benchmark.c
+++ b/app/test-dma-perf/benchmark.c
@@ -313,7 +313,8 @@ setup_memory_env(struct test_configure *cfg, struct rte_mbuf ***srcs,
nr_sockets = rte_socket_count();
if (cfg->src_numa_node >= nr_sockets ||
cfg->dst_numa_node >= nr_sockets) {
- printf("Error: Source or destination numa exceeds the acture numa nodes.\n");
+ printf("Error: %s numa exceeds the available numa nodes.\n",
+ (cfg->src_numa_node >= nr_sockets) ? "Source" : "Destination");
return -1;
}
--
2.40.1
next reply other threads:[~2024-03-06 15:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 15:02 Vipin Varghese [this message]
2024-03-07 13:19 ` fengchengwen
2024-03-07 16:06 ` Varghese, Vipin
2024-03-11 6:00 ` [PATCH v2] " Vipin Varghese
2024-03-12 2:10 ` fengchengwen
2024-03-12 3:48 ` Varghese, Vipin
2024-03-13 9:37 ` Konstantin Ananyev
2024-03-20 1:14 ` Varghese, Vipin
2024-03-20 1:40 ` [PATCH v3] " Vipin Varghese
2024-11-19 17:07 ` Thomas Monjalon
2024-11-19 17:56 ` [EXTERNAL] " Gowrishankar Muthukrishnan
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=20240306150204.1375-1-vipin.varghese@amd.com \
--to=vipin.varghese@amd.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@amd.com \
--cc=neerav.parikh@amd.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).