From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH] net/tap: allow more that 4 queues
Date: Thu, 29 Feb 2024 09:56:18 -0800 [thread overview]
Message-ID: <20240229175620.122949-1-stephen@networkplumber.org> (raw)
The tap device needs to exchange file descriptors for tx and rx.
But the EAL MP layer has limit of 8 file descriptors per message.
The ideal resolution would be to increase the number of file
descriptors allowed for rte_mp_sendmsg(), but this would break
the ABI. Workaround the constraint by breaking into multiple messages.
Do not hide errors about MP message failures.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
drivers/net/tap/rte_eth_tap.c | 40 +++++++++++++++++++++++++++++------
1 file changed, 33 insertions(+), 7 deletions(-)
diff --git a/drivers/net/tap/rte_eth_tap.c b/drivers/net/tap/rte_eth_tap.c
index 69d9da695bed..df18c328f498 100644
--- a/drivers/net/tap/rte_eth_tap.c
+++ b/drivers/net/tap/rte_eth_tap.c
@@ -863,21 +863,44 @@ tap_mp_req_on_rxtx(struct rte_eth_dev *dev)
msg.fds[fd_iterator++] = process_private->txq_fds[i];
msg.num_fds++;
request_param->txq_count++;
+
+ /* Need to break request into chunks */
+ if (fd_iterator >= RTE_MP_MAX_FD_NUM) {
+ err = rte_mp_sendmsg(&msg);
+ if (err < 0)
+ goto fail;
+
+ fd_iterator = 0;
+ msg.num_fds = 0;
+ request_param->txq_count = 0;
+ }
}
for (i = 0; i < dev->data->nb_rx_queues; i++) {
msg.fds[fd_iterator++] = process_private->rxq_fds[i];
msg.num_fds++;
request_param->rxq_count++;
+
+ if (fd_iterator >= RTE_MP_MAX_FD_NUM) {
+ err = rte_mp_sendmsg(&msg);
+ if (err < 0)
+ goto fail;
+
+ fd_iterator = 0;
+ msg.num_fds = 0;
+ request_param->rxq_count = 0;
+ }
}
- err = rte_mp_sendmsg(&msg);
- if (err < 0) {
- TAP_LOG(ERR, "Failed to send start req to secondary %d",
- rte_errno);
- return -1;
+ if (msg.num_fds > 0) {
+ err = rte_mp_sendmsg(&msg);
+ if (err < 0)
+ goto fail;
}
return 0;
+fail:
+ TAP_LOG(ERR, "Failed to send start req to secondary %d", rte_errno);
+ return err;
}
static int
@@ -885,8 +908,11 @@ tap_dev_start(struct rte_eth_dev *dev)
{
int err, i;
- if (rte_eal_process_type() == RTE_PROC_PRIMARY)
- tap_mp_req_on_rxtx(dev);
+ if (rte_eal_process_type() == RTE_PROC_PRIMARY) {
+ err = tap_mp_req_on_rxtx(dev);
+ if (err)
+ return err;
+ }
err = tap_intr_handle_set(dev, 1);
if (err)
--
2.43.0
next reply other threads:[~2024-02-29 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 17:56 Stephen Hemminger [this message]
2024-03-06 16:14 ` Ferruh Yigit
2024-03-06 20:21 ` Stephen Hemminger
2024-03-07 10:25 ` Ferruh Yigit
2024-03-07 16:53 ` Stephen Hemminger
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=20240229175620.122949-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--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).