DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Han, YingyaX" <yingyax.han@intel.com>
To: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
	"dev@dpdk.org" <dev@dpdk.org>, "Tu, Lijuan" <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>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	"stephen@networkplumber.org" <stephen@networkplumber.org>,
	"bluca@debian.org" <bluca@debian.org>,
	"ktraynor@redhat.com" <ktraynor@redhat.com>,
	"christian.ehrhardt@canonical.com"
	<christian.ehrhardt@canonical.com>,
	"xuemingl@nvidia.com" <xuemingl@nvidia.com>
Cc: "kathleen.capella@arm.com" <kathleen.capella@arm.com>,
	"nd@arm.com" <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: Tue, 1 Mar 2022 01:56:50 +0000	[thread overview]
Message-ID: <DM5PR11MB127608995116ADAA03E727CDFF029@DM5PR11MB1276.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220223060931.2661907-1-honnappa.nagarahalli@arm.com>



-----Original Message-----
From: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> 
Sent: Wednesday, February 23, 2022 2:10 PM
To: dev@dpdk.org; honnappa.nagarahalli@arm.com; Tu, Lijuan <lijuan.tu@intel.com>; juraj.linkes@pantheon.tech; ohilyard@iol.unh.edu; david.marchand@redhat.com; thomas@monjalon.net; jerinj@marvell.com; Richardson, Bruce <bruce.richardson@intel.com>; stephen@networkplumber.org; bluca@debian.org; ktraynor@redhat.com; christian.ehrhardt@canonical.com; xuemingl@nvidia.com
Cc: kathleen.capella@arm.com; 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>

Tested-by: Yingya Han < yingyax.han@intel.com>

  parent reply	other threads:[~2022-03-01  1:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02  6:04 [PATCH " Honnappa Nagarahalli
2022-02-02  6:04 ` [PATCH 2/2] examples/l3fwd: make RX and TX queue size configurable Honnappa Nagarahalli
2022-02-08  7:41   ` Ruifeng Wang
2022-02-02  8:49 ` [PATCH 1/2] examples/l3fwd: use single set of variables throughout the code Bruce Richardson
2022-02-11  0:26 ` [PATCH v2 " Honnappa Nagarahalli
2022-02-11  0:26   ` [PATCH v2 2/2] examples/l3fwd: make RX and TX queue size configurable Honnappa Nagarahalli
2022-02-11  0:53     ` Stephen Hemminger
2022-02-11  3:43       ` Honnappa Nagarahalli
2022-02-11  1:01     ` Stephen Hemminger
2022-02-11  3:38       ` Honnappa Nagarahalli
2022-02-23  6:09 ` [PATCH v3 1/2] examples/l3fwd: use single set of variables throughout the code Honnappa Nagarahalli
2022-02-23  6:09   ` [PATCH v3 2/2] examples/l3fwd: make RX and TX queue size configurable Honnappa Nagarahalli
2022-02-23  6:13   ` [PATCH v3 1/2] examples/l3fwd: use single set of variables throughout the code Honnappa Nagarahalli
2022-02-23  9:22     ` Kevin Traynor
2022-03-01  1:56   ` Han, YingyaX [this message]
2022-03-08  9:22     ` 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=DM5PR11MB127608995116ADAA03E727CDFF029@DM5PR11MB1276.namprd11.prod.outlook.com \
    --to=yingyax.han@intel.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=honnappa.nagarahalli@arm.com \
    --cc=jerinj@marvell.com \
    --cc=juraj.linkes@pantheon.tech \
    --cc=kathleen.capella@arm.com \
    --cc=ktraynor@redhat.com \
    --cc=lijuan.tu@intel.com \
    --cc=nd@arm.com \
    --cc=ohilyard@iol.unh.edu \
    --cc=ruifeng.wang@arm.com \
    --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).