From: Ferruh Yigit <ferruh.yigit@amd.com>
To: fengchengwen <fengchengwen@huawei.com>,
Huisong Li <lihuisong@huawei.com>,
dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: liuyonglong@huawei.com
Subject: Re: [PATCH] ethdev: add trace for the new fields added in 23.11
Date: Tue, 21 Nov 2023 12:12:32 +0000 [thread overview]
Message-ID: <00ac70e6-24de-4b1f-86a6-051d9a22136c@amd.com> (raw)
In-Reply-To: <fe896971-8d1c-77d8-a3e3-81a801338cc2@huawei.com>
On 11/21/2023 8:29 AM, fengchengwen wrote:
> On 2023/11/21 16:18, Huisong Li wrote:
>> The 'max_rx_bufsize' and 'rss_algo_capa' in struct rte_eth_dev_info and
>> the 'algorithm' in struct rte_eth_rss_conf are introduced to 23.11.
>> This patch add the trace of these new fields in related trace point
>> interface.
>>
>> In addition, the 'max_lro_pkt_size' in struct rte_eth_dev_info is also
>> important. So this patch also add it.
>>
>> Signed-off-by: Huisong Li <lihuisong@huawei.com>
>
> Acked-by: Chengwen Feng <fengchengwen@huawei.com>
>
Fixes: 75c7849a9dcc ("ethdev: add maximum Rx buffer size")
Fixes: 34ff088cc241 ("ethdev: set and query RSS hash algorithm")
Reviewed-by: Ferruh Yigit <ferruh.yigit@amd.com>
'max_lro_pkt_size' seems forgotten, and it is not a new field, so patch
adding it should be backported to old releases.
That is why I removed the 'max_lro_pkt_size' from this patch and updated
commit log accordingly, Will send a separate patch for it.
Applied to dpdk-next-net/main, thanks.
next prev parent reply other threads:[~2023-11-21 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 8:18 Huisong Li
2023-11-21 8:29 ` fengchengwen
2023-11-21 12:12 ` Ferruh Yigit [this message]
2023-11-21 12:39 ` lihuisong (C)
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=00ac70e6-24de-4b1f-86a6-051d9a22136c@amd.com \
--to=ferruh.yigit@amd.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=lihuisong@huawei.com \
--cc=liuyonglong@huawei.com \
--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).