From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 0/3] make struct parameters constant in rte_tm APIs
Date: Tue, 8 Oct 2024 01:38:30 +0100 [thread overview]
Message-ID: <d09b52d6-84d9-4e9f-8ea6-71d1d8e8126b@amd.com> (raw)
In-Reply-To: <20241007082207.27f1f01d@hermes.local>
On 10/7/2024 4:22 PM, Stephen Hemminger wrote:
> On Mon, 7 Oct 2024 12:49:04 +0100
> Bruce Richardson <bruce.richardson@intel.com> wrote:
>
>> For functions for creating profiles, shapers and hierarchy nodes, make
>> the parameter structure pointer a pointer to a const object. This
>> guarantees to the user that the struct won't be modified by the
>> function, which allows the user to re-use the same parameters multiple
>> times without having to constantly reinitialize it.
>>
>> V2: drop final patch with new node query function, simplifying patchset
>>
>> Bruce Richardson (3):
>> ethdev: make parameters to TM node add fn constant
>> ethdev: make parameters to TM profile add fn constant
>> ethdev: make TM shaper parameters constant
>>
>> drivers/net/cnxk/cnxk_tm.c | 4 ++--
>> drivers/net/dpaa2/dpaa2_tm.c | 6 +++---
>> drivers/net/hns3/hns3_tm.c | 22 +++++++++++-----------
>> drivers/net/i40e/i40e_tm.c | 12 ++++++------
>> drivers/net/iavf/iavf_tm.c | 12 ++++++------
>> drivers/net/ice/ice_dcf_sched.c | 12 ++++++------
>> drivers/net/ice/ice_tm.c | 12 ++++++------
>> drivers/net/ipn3ke/ipn3ke_tm.c | 12 ++++++------
>> drivers/net/ixgbe/ixgbe_tm.c | 12 ++++++------
>> drivers/net/mvpp2/mrvl_tm.c | 2 +-
>> drivers/net/txgbe/txgbe_tm.c | 12 ++++++------
>> lib/ethdev/rte_tm.c | 6 +++---
>> lib/ethdev/rte_tm.h | 6 +++---
>> lib/ethdev/rte_tm_driver.h | 6 +++---
>> 14 files changed, 68 insertions(+), 68 deletions(-)
>>
>> --
>> 2.43.0
>>
>
> Series-Acked-by: Stephen Hemminger <stephen@networkplumber.org>
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2024-10-08 0:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 15:24 [PATCH 0/4] improve rte_tm APIs Bruce Richardson
2024-08-06 15:24 ` [PATCH 1/4] ethdev: make parameters to TM node add fn constant Bruce Richardson
2024-08-07 7:27 ` Xu, Rosen
2024-09-22 16:10 ` Ferruh Yigit
2024-08-06 15:24 ` [PATCH 2/4] ethdev: make parameters to TM profile " Bruce Richardson
2024-08-07 7:27 ` Xu, Rosen
2024-09-22 16:11 ` Ferruh Yigit
2024-08-06 15:24 ` [PATCH 3/4] ethdev: make TM shaper parameters constant Bruce Richardson
2024-08-07 7:29 ` Xu, Rosen
2024-09-22 16:11 ` Ferruh Yigit
2024-08-06 15:24 ` [PATCH 4/4] ethdev: add traffic manager query function Bruce Richardson
2024-09-22 16:26 ` Ferruh Yigit
2024-10-07 11:04 ` Bruce Richardson
2024-10-08 10:56 ` Bruce Richardson
2024-10-07 11:49 ` [PATCH v2 0/3] make struct parameters constant in rte_tm APIs Bruce Richardson
2024-10-07 11:49 ` [PATCH v2 1/3] ethdev: make parameters to TM node add fn constant Bruce Richardson
2024-10-07 11:49 ` [PATCH v2 2/3] ethdev: make parameters to TM profile " Bruce Richardson
2024-10-07 11:49 ` [PATCH v2 3/3] ethdev: make TM shaper parameters constant Bruce Richardson
2024-10-07 15:22 ` [PATCH v2 0/3] make struct parameters constant in rte_tm APIs Stephen Hemminger
2024-10-08 0:38 ` Ferruh Yigit [this message]
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=d09b52d6-84d9-4e9f-8ea6-71d1d8e8126b@amd.com \
--to=ferruh.yigit@amd.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.