From: Kalesh AP <kalesh-anakkur.pura...@broadcom.com>

Broadcom HW drops packets when there are no descriptors available.
It does not matter what flag the application specifies in "rx_drop_en"
when configuring the Rx ring.

Reduce the verbosity of the log to print the status of the "rx_drop_en"
when configuring the Rx ring.

Signed-off-by: Kalesh AP <kalesh-anakkur.pura...@broadcom.com>
Reviewed-by: Somnath Kotur <somnath.ko...@broadcom.com>
Reviewed-by: Ajit Khaparde <ajit.khapa...@broadcom.com>
---
 drivers/net/bnxt/bnxt_rxq.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/drivers/net/bnxt/bnxt_rxq.c b/drivers/net/bnxt/bnxt_rxq.c
index ef2ef83..f4b6417 100644
--- a/drivers/net/bnxt/bnxt_rxq.c
+++ b/drivers/net/bnxt/bnxt_rxq.c
@@ -360,9 +360,8 @@ int bnxt_rx_queue_setup_op(struct rte_eth_dev *eth_dev,
        rxq->rx_free_thresh =
                RTE_MIN(rte_align32pow2(nb_desc) / 4, RTE_BNXT_MAX_RX_BURST);
 
-       if (rx_conf->rx_drop_en != BNXT_DEFAULT_RX_DROP_EN)
-               PMD_DRV_LOG(NOTICE,
-                           "Per-queue config of drop-en is not supported.\n");
+       PMD_DRV_LOG(DEBUG,
+                   "App supplied RXQ drop_en status : %d\n", 
rx_conf->rx_drop_en);
        rxq->drop_en = BNXT_DEFAULT_RX_DROP_EN;
 
        PMD_DRV_LOG(DEBUG, "RX Buf MTU %d\n", eth_dev->data->mtu);
-- 
2.10.1

Reply via email to