The "min_rx_bufsize" in struct rte_eth_dev_info stands for the minimum Rx buffer size supported by hardware. Actually, some engines also have the maximum Rx buffer specification, like, hns3.
If mbuf data room size in mempool is greater then the maximum Rx buffer size supported by HW, the data size application used in each mbuf is just as much as the maximum Rx buffer size supported by HW instead of the whole data room size. So introduce maximum Rx buffer size which is not enforced just to report user to avoid memory waste. --- v5: - fix a valiable name - fix the log level and context in rte_eth_rx_queue_setup. v4: - fix the log in rte_eth_rx_queue_setup. - add a comment in rel_notes. v3: - fix some comments for Morten's advice. v2: - fix some comments - fix the log level when data room size is greater than maximum Rx buffer size. v1: - move max_rx_bufsize to min_rx_bufsize closer in struct rte_eth_dev_info - add max_rx_bufsize display in testpmd. - hns3 reports maximum buffer size. Huisong Li (3): ethdev: introduce maximum Rx buffer size app/testpmd: add maximum Rx buffer size display net/hns3: report maximum buffer size app/test-pmd/config.c | 2 ++ doc/guides/rel_notes/release_23_11.rst | 7 +++++++ drivers/net/hns3/hns3_common.c | 1 + lib/ethdev/rte_ethdev.c | 8 ++++++++ lib/ethdev/rte_ethdev.h | 10 +++++++++- 5 files changed, 27 insertions(+), 1 deletion(-) -- 2.33.0
