From: Thomas Monjalon <thomas@monjalon.net>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: Jerin Jacob <jerinjacobk@gmail.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Kathleen Capella <Kathleen.Capella@arm.com>,
Dharmik Thakkar <Dharmik.Thakkar@arm.com>,
Ruifeng Wang <Ruifeng.Wang@arm.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
Bruce Richardson <bruce.richardson@intel.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
Stephen Hemminger <sthemmin@microsoft.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] L3fwd mode in testpmd
Date: Thu, 11 Mar 2021 16:46:22 +0100 [thread overview]
Message-ID: <2273212.ItJIoklBD0@thomas> (raw)
In-Reply-To: <DBAPR08MB5814BA72850E0D33B4B918B898909@DBAPR08MB5814.eurprd08.prod.outlook.com>
11/03/2021 16:18, Honnappa Nagarahalli:
> <snip>
>
> >
> > On Thu, Mar 11, 2021 at 12:01 AM Honnappa Nagarahalli
> > <Honnappa.Nagarahalli@arm.com> wrote:
> > >
> > > Hello,
> > > Performance of L3fwd example application is one of the key
> > benchmarks in DPDK. However, the application does not have many
> > debugging statistics to understand the performance issues. We have added
> > L3fwd as another mode/stream to testpmd which provides enough statistics
> > at various levels. This has allowed us to debug the performance issues
> > effectively.
> > >
> > > There is more work to be done to get it to upstreamable state. I am
> > wondering if such a patch is helpful for others and if the community would
> > be interested in taking a look. Please let me know what you think.
> >
> > We are using app/proc-info/ to attach and analyze the performance.
> > That helps to analyze the unmodified application. I think, if something is
> > missing in proc-info app, in my opinion it is better to enhance proc-info so
> > that it can help other third-party applications.
> >
> > Just my 2c.
> Thanks Jerin. We will explore that.
I agree it is dangerous to rely too much on testpmd for everything.
Please tell us what in testpmd could be useful out of it.
next prev parent reply other threads:[~2021-03-11 15:46 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 18:31 Honnappa Nagarahalli
2021-03-11 6:41 ` Jerin Jacob
2021-03-11 15:18 ` Honnappa Nagarahalli
2021-03-11 15:46 ` Thomas Monjalon [this message]
2021-03-11 16:00 ` Honnappa Nagarahalli
2021-03-31 20:35 ` Kathleen Capella
2021-03-31 21:17 ` Jerin Jacob
2021-04-01 0:20 ` Honnappa Nagarahalli
2021-04-01 4:38 ` Jerin Jacob
2021-04-24 0:26 ` Honnappa Nagarahalli
2021-04-26 9:44 ` Jerin Jacob
2021-04-26 17:47 ` Stephen Hemminger
2021-04-26 20:46 ` Honnappa Nagarahalli
2021-04-27 9:39 ` Andrew Rybchenko
2021-04-27 9:50 ` Ferruh Yigit
2021-04-27 9:57 ` Ananyev, Konstantin
2021-04-27 11:11 ` Thomas Monjalon
2021-04-27 11:32 ` Bruce Richardson
2021-04-27 23:26 ` Honnappa Nagarahalli
2021-04-27 23:17 ` Honnappa Nagarahalli
2021-04-28 10:48 ` Bruce Richardson
2021-04-28 11:04 ` Stanisław Kardach
2021-04-28 11:19 ` Thomas Monjalon
2021-04-28 21:44 ` Honnappa Nagarahalli
2021-04-29 7:49 ` Stanislaw Kardach
2021-04-29 8:31 ` Ananyev, Konstantin
2021-04-29 10:39 ` Stanislaw Kardach
2021-04-29 11:47 ` Ananyev, Konstantin
2021-04-29 11:53 ` Stanislaw Kardach
2021-04-30 11:28 ` Ananyev, Konstantin
2021-08-02 15:07 ` Dharmik Thakkar
2021-04-28 11:17 ` Thomas Monjalon
2021-04-28 10:59 ` Ananyev, Konstantin
2021-04-28 22:10 ` Honnappa Nagarahalli
2021-04-27 16:01 ` Stephen Hemminger
2021-04-27 20:20 ` Honnappa Nagarahalli
2021-04-27 22:23 ` Ananyev, Konstantin
2021-04-27 23:11 ` Honnappa Nagarahalli
2021-04-28 11:00 ` Ananyev, Konstantin
2021-04-26 20:32 ` Honnappa Nagarahalli
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=2273212.ItJIoklBD0@thomas \
--to=thomas@monjalon.net \
--cc=Dharmik.Thakkar@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Kathleen.Capella@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=konstantin.ananyev@intel.com \
--cc=nd@arm.com \
--cc=sthemmin@microsoft.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).