patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"lijuan.tu@intel.com" <lijuan.tu@intel.com>,
	"juraj.linkes@pantheon.tech" <juraj.linkes@pantheon.tech>,
	"ohilyard@iol.unh.edu" <ohilyard@iol.unh.edu>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	"jerinj@marvell.com" <jerinj@marvell.com>,
	"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
	"stephen@networkplumber.org" <stephen@networkplumber.org>,
	"bluca@debian.org" <bluca@debian.org>,
	"christian.ehrhardt@canonical.com"
	<christian.ehrhardt@canonical.com>,
	"xuemingl@nvidia.com" <xuemingl@nvidia.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Cc: Kathleen Capella <Kathleen.Capella@arm.com>, nd <nd@arm.com>,
	Ruifeng Wang <Ruifeng.Wang@arm.com>
Subject: Re: [PATCH v3 1/2] examples/l3fwd: use single set of variables throughout the code
Date: Wed, 23 Feb 2022 09:22:33 +0000	[thread overview]
Message-ID: <1fb40c72-8a5c-ba53-73bc-8bc4a139542f@redhat.com> (raw)
In-Reply-To: <DBAPR08MB5814D5957FA7CC420B86EBA8983C9@DBAPR08MB5814.eurprd08.prod.outlook.com>

Hi Honnappa,

On 23/02/2022 06:13, Honnappa Nagarahalli wrote:
> Question for stable maintainers.
> 
> DTS WG would like this patch to be merged in 21.11 and 20.11 stable releases even though it is not a bug fix. This allows for a single DTS version to be used with both those stable releases and master.
> 
> Do you have any objections?
> 

No objection for 21.11. It is example code and just a minor addition 
that is not changing defaults. Please add the stable tag in the commit 
message on merge (or next rev) so it will be found by our scripts.

thanks,
Kevin.

> Thank you,
> Honnappa
> 
> 
>> -----Original Message-----
>> From: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
>> Sent: Wednesday, February 23, 2022 12:10 AM
>> To: dev@dpdk.org; Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>;
>> lijuan.tu@intel.com; juraj.linkes@pantheon.tech; ohilyard@iol.unh.edu;
>> david.marchand@redhat.com; thomas@monjalon.net; jerinj@marvell.com;
>> bruce.richardson@intel.com; stephen@networkplumber.org;
>> bluca@debian.org; ktraynor@redhat.com; christian.ehrhardt@canonical.com;
>> xuemingl@nvidia.com
>> Cc: Kathleen Capella <Kathleen.Capella@arm.com>; nd <nd@arm.com>;
>> Ruifeng Wang <Ruifeng.Wang@arm.com>
>> Subject: [PATCH v3 1/2] examples/l3fwd: use single set of variables throughout
>> the code
>>
>> nb_rxd and nb_txd are used in polling mode and event mode of operation.
>> nb_rxd and nb_txd are already global in polling mode but are not visible to
>> event mode code. Make them visible to all parts of the application.
>>
>> Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
>> Reviewed-by: Kathleen Capella <kathleen.capella@arm.com>
>> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
>> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
>> ---
>> DTS test cases require changing the RX and TX queue depths.
>> Currently, this is achieved by patching the DPDK code. This patch set provides a
>> mechanism to configure the queue depths while launching the application. With
>> this change DTS test cases do not need to modify the DPDK code.
>>
>> v2 - Single parse function, additional validation on input (Stephen)
>>
>> v2 - Fixed typo (Ruifeng) and adjusted the commit msg (Kathleen).
>>
>>   examples/l3fwd/l3fwd.h       | 4 ++++
>>   examples/l3fwd/l3fwd_event.c | 2 --
>>   examples/l3fwd/main.c        | 5 ++---
>>   3 files changed, 6 insertions(+), 5 deletions(-)
>>
>> diff --git a/examples/l3fwd/l3fwd.h b/examples/l3fwd/l3fwd.h index
>> 38ca19133c..4ccdb28b4a 100644
>> --- a/examples/l3fwd/l3fwd.h
>> +++ b/examples/l3fwd/l3fwd.h
>> @@ -81,6 +81,10 @@ struct lcore_conf {
>>
>>   extern volatile bool force_quit;
>>
>> +/* RX and TX queue depths */
>> +extern uint16_t nb_rxd;
>> +extern uint16_t nb_txd;
>> +
>>   /* ethernet addresses of ports */
>>   extern uint64_t dest_eth_addr[RTE_MAX_ETHPORTS];  extern struct
>> rte_ether_addr ports_eth_addr[RTE_MAX_ETHPORTS]; diff --git
>> a/examples/l3fwd/l3fwd_event.c b/examples/l3fwd/l3fwd_event.c index
>> dd9eafa9b9..7a401290f8 100644
>> --- a/examples/l3fwd/l3fwd_event.c
>> +++ b/examples/l3fwd/l3fwd_event.c
>> @@ -43,8 +43,6 @@ l3fwd_eth_dev_port_setup(struct rte_eth_conf
>> *port_conf)  {
>>   	struct l3fwd_event_resources *evt_rsrc = l3fwd_get_eventdev_rsrc();
>>   	uint16_t nb_ports = rte_eth_dev_count_avail();
>> -	uint16_t nb_rxd = RTE_TEST_RX_DESC_DEFAULT;
>> -	uint16_t nb_txd = RTE_TEST_TX_DESC_DEFAULT;
>>   	unsigned int nb_lcores = rte_lcore_count();
>>   	struct rte_eth_conf local_port_conf;
>>   	struct rte_eth_dev_info dev_info;
>> diff --git a/examples/l3fwd/main.c b/examples/l3fwd/main.c index
>> eb68ffc5aa..acd186ab7d 100644
>> --- a/examples/l3fwd/main.c
>> +++ b/examples/l3fwd/main.c
>> @@ -53,9 +53,8 @@
>>
>>   #define MAX_LCORE_PARAMS 1024
>>
>> -/* Static global variables used within this file. */ -static uint16_t nb_rxd =
>> RTE_TEST_RX_DESC_DEFAULT; -static uint16_t nb_txd =
>> RTE_TEST_TX_DESC_DEFAULT;
>> +uint16_t nb_rxd = RTE_TEST_RX_DESC_DEFAULT; uint16_t nb_txd =
>> +RTE_TEST_TX_DESC_DEFAULT;
>>
>>   /**< Ports set in promiscuous mode off by default. */  static int
>> promiscuous_on;
>> --
>> 2.25.1
> 


      reply	other threads:[~2022-02-23  9:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220202060403.118301-1-honnappa.nagarahalli@arm.com>
     [not found] ` <20220223060931.2661907-1-honnappa.nagarahalli@arm.com>
2022-02-23  6:13   ` Honnappa Nagarahalli
2022-02-23  9:22     ` Kevin Traynor [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=1fb40c72-8a5c-ba53-73bc-8bc4a139542f@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=Kathleen.Capella@arm.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=bluca@debian.org \
    --cc=bruce.richardson@intel.com \
    --cc=christian.ehrhardt@canonical.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=juraj.linkes@pantheon.tech \
    --cc=lijuan.tu@intel.com \
    --cc=nd@arm.com \
    --cc=ohilyard@iol.unh.edu \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    --cc=xuemingl@nvidia.com \
    /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).