DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Chaoyong He" <chaoyong.he@corigine.com>, <dev@dpdk.org>
Cc: <oss-drivers@corigine.com>, <niklas.soderlund@corigine.com>,
	"Long Wu" <long.wu@corigine.com>, <stephen@networkplumber.org>,
	"Ferruh Yigit" <ferruh.yigit@amd.com>,
	"Huisong Li" <lihuisong@huawei.com>
Subject: RE: [PATCH v3 1/3] doc: announce bonding macro change
Date: Wed, 26 Jul 2023 13:47:00 +0200	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D87A85@smartserver.smartshare.dk> (raw)
In-Reply-To: <20230718082856.2235450-2-chaoyong.he@corigine.com>

> From: Chaoyong He [mailto:chaoyong.he@corigine.com]
> Sent: Tuesday, 18 July 2023 10.29
> 
> From: Long Wu <long.wu@corigine.com>
> 
> In order to support inclusive naming, some of the macro in DPDK will
> need to be renamed. Do this through deprecation process now for 23.07.
> 
> Signed-off-by: Long Wu <long.wu@corigine.com>
> Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
> ---
>  app/test-pmd/testpmd.c                 | 2 +-
>  doc/guides/rel_notes/deprecation.rst   | 4 ++++
>  drivers/net/bonding/rte_eth_bond_api.c | 6 +++---
>  lib/ethdev/rte_ethdev.h                | 5 +++--
>  4 files changed, 11 insertions(+), 6 deletions(-)
> 
> diff --git a/app/test-pmd/testpmd.c b/app/test-pmd/testpmd.c
> index c6ad9b18bf..938ca035d4 100644
> --- a/app/test-pmd/testpmd.c
> +++ b/app/test-pmd/testpmd.c
> @@ -4248,7 +4248,7 @@ uint8_t port_is_bonding_slave(portid_t slave_pid)
>  			slave_pid);

We might want to get rid of the term "slave" in function, parameter and variable names in testpmd too. This is not important now, and can be postponed to a later patch.

>  		return 0;
>  	}
> -	if ((*dev_info.dev_flags & RTE_ETH_DEV_BONDED_SLAVE) || (port-
> >slave_flag == 1))
> +	if ((*dev_info.dev_flags & RTE_ETH_DEV_BONDING_MEMBER) || (port-
> >slave_flag == 1))

Can we please standardize on using only "bond" and "BOND" everywhere in this driver, instead of both "bond" (in function names) and "BONDING" (in enum values)?

The source code file are also named "rte_eth_bond...", while the directory name is /drivers/net/bonding/.

We are about to rename anyway, so let's do it as good as we can.


Also, are the bonding and balancing modes defined in /drivers/net/bonding/rte_eth_bond.h missing the RTE_ prefix, or are they private?


PS: Sorry about joining the discussion late (and possibly ignoring previous discussions on this). I reacted to the poll for ACKs to this series.


  parent reply	other threads:[~2023-07-26 11:47 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14  8:15 [PATCH 0/3] announce bonding macro and function change Chaoyong He
2023-07-14  8:15 ` [PATCH 1/3] doc: announce bonding macro change Chaoyong He
2023-07-17 15:13   ` Ferruh Yigit
2023-07-18  1:17     ` Chaoyong He
2023-07-14  8:15 ` [PATCH 2/3] doc: announce bonding data change Chaoyong He
2023-07-17 15:03   ` Ferruh Yigit
2023-07-18  1:13     ` Chaoyong He
2023-07-14  8:15 ` [PATCH 3/3] doc: announce bonding function change Chaoyong He
2023-07-17 15:13   ` Ferruh Yigit
2023-07-18  1:15     ` Chaoyong He
2023-07-17 15:14 ` [PATCH 0/3] announce bonding macro and " Ferruh Yigit
2023-07-18  1:48 ` [PATCH v2 " Chaoyong He
2023-07-18  1:48   ` [PATCH v2 1/3] doc: announce bonding macro change Chaoyong He
2023-07-18  8:09     ` Ferruh Yigit
2023-07-18  1:48   ` [PATCH v2 2/3] doc: announce bonding data change Chaoyong He
2023-07-18  8:05     ` Ferruh Yigit
2023-07-18  1:48   ` [PATCH v2 3/3] doc: announce bonding function change Chaoyong He
2023-07-18  8:05     ` Ferruh Yigit
2023-07-18  8:28   ` [PATCH v3 0/3] announce bonding macro and " Chaoyong He
2023-07-18  8:28     ` [PATCH v3 1/3] doc: announce bonding macro change Chaoyong He
2023-07-18 11:39       ` Ferruh Yigit
2023-07-18 15:53       ` Stephen Hemminger
2023-07-19  1:24       ` lihuisong (C)
2023-07-26 11:47       ` Morten Brørup [this message]
2023-07-18  8:28     ` [PATCH v3 2/3] doc: announce bonding data change Chaoyong He
2023-07-18 11:40       ` Ferruh Yigit
2023-07-18 15:53       ` Stephen Hemminger
2023-07-19  1:32       ` lihuisong (C)
2023-07-18  8:28     ` [PATCH v3 3/3] doc: announce bonding function change Chaoyong He
2023-07-18 11:40       ` Ferruh Yigit
2023-07-18 15:52       ` Stephen Hemminger
2023-07-19  1:31       ` lihuisong (C)
2023-07-19  1:37         ` Chaoyong He
2023-07-19  1:53           ` lihuisong (C)
2023-07-26  9:06     ` [PATCH v3 0/3] announce bonding macro and " Chaoyong He
2023-07-28 13:54     ` Thomas Monjalon

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=98CBD80474FA8B44BF855DF32C47DC35D87A85@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=chaoyong.he@corigine.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=lihuisong@huawei.com \
    --cc=long.wu@corigine.com \
    --cc=niklas.soderlund@corigine.com \
    --cc=oss-drivers@corigine.com \
    --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 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).