From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ankur Dwivedi <adwivedi@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>
Cc: <dev@dpdk.org>, Huisong Li <lihuisong@huawei.com>,
<stable@dpdk.org>, Chengwen Feng <fengchengwen@huawei.com>
Subject: [PATCH] ethdev: add trace for max LRO
Date: Tue, 21 Nov 2023 12:28:53 +0000 [thread overview]
Message-ID: <20231121122854.1211046-1-ferruh.yigit@amd.com> (raw)
From: Huisong Li <lihuisong@huawei.com>
The 'max_lro_pkt_size' in struct rte_eth_dev_info is also important.
So this patch also add it.
Fixes: 6679cf21d608 ("ethdev: add trace points")
Cc: stable@dpdk.org
Signed-off-by: Huisong Li <lihuisong@huawei.com>
Acked-by: Chengwen Feng <fengchengwen@huawei.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@amd.com>
---
Cc: adwivedi@marvell.com
---
lib/ethdev/ethdev_trace.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/lib/ethdev/ethdev_trace.h b/lib/ethdev/ethdev_trace.h
index 8bc0abc2a2ae..1b1ae0cfe8cf 100644
--- a/lib/ethdev/ethdev_trace.h
+++ b/lib/ethdev/ethdev_trace.h
@@ -32,6 +32,7 @@ RTE_TRACE_POINT(
rte_trace_point_emit_u32(dev_conf->link_speeds);
rte_trace_point_emit_u32(dev_conf->rxmode.mq_mode);
rte_trace_point_emit_u32(dev_conf->rxmode.mtu);
+ rte_trace_point_emit_u32(dev_conf->rxmode.max_lro_pkt_size);
rte_trace_point_emit_u64(dev_conf->rxmode.offloads);
rte_trace_point_emit_u32(dev_conf->txmode.mq_mode);
rte_trace_point_emit_u64(dev_conf->txmode.offloads);
@@ -558,6 +559,7 @@ RTE_TRACE_POINT(
rte_trace_point_emit_u32(dev_info->min_rx_bufsize);
rte_trace_point_emit_u32(dev_info->max_rx_bufsize);
rte_trace_point_emit_u32(dev_info->max_rx_pktlen);
+ rte_trace_point_emit_u32(dev_info->max_lro_pkt_size);
rte_trace_point_emit_u16(dev_info->max_rx_queues);
rte_trace_point_emit_u16(dev_info->max_tx_queues);
rte_trace_point_emit_u32(dev_info->max_mac_addrs);
--
2.34.1
reply other threads:[~2023-11-21 12:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231121122854.1211046-1-ferruh.yigit@amd.com \
--to=ferruh.yigit@amd.com \
--cc=adwivedi@marvell.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=lihuisong@huawei.com \
--cc=skori@marvell.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).