[PATCH v2 1/3] net/tap: handle increase in mp_max_fds

[Stephen Hemminger]

Now that max MP fds has increased to 253 it is possible that
the number of queues the TAP device can handle is less than that.
Therefore the code to handle MP message should only allow the
number of queues it can handle.

Coverity issue: 445386
Signed-off-by: Stephen Hemminger <step...@networkplumber.org>
---
 drivers/net/tap/rte_eth_tap.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/drivers/net/tap/rte_eth_tap.c b/drivers/net/tap/rte_eth_tap.c
index 5ad3bbadd1..c486c6f073 100644
--- a/drivers/net/tap/rte_eth_tap.c
+++ b/drivers/net/tap/rte_eth_tap.c
@@ -2391,9 +2391,10 @@ tap_mp_sync_queues(const struct rte_mp_msg *request, 
const void *peer)
        reply_param->q_count = 0;
 
        RTE_ASSERT(dev->data->nb_rx_queues == dev->data->nb_tx_queues);
-       if (dev->data->nb_rx_queues > RTE_MP_MAX_FD_NUM) {
+
+       if (dev->data->nb_rx_queues > RTE_PMD_TAP_MAX_QUEUES) {
                TAP_LOG(ERR, "Number of rx/tx queues %u exceeds max number of 
fds %u",
-                       dev->data->nb_rx_queues, RTE_MP_MAX_FD_NUM);
+                       dev->data->nb_rx_queues, RTE_PMD_TAP_MAX_QUEUES);
                return -1;
        }
 
-- 
2.45.2