DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Ben Pfaff <blp@ovn.org>, dpdk-dev <dev@dpdk.org>,
	Xiaoyun Li <xiaoyun.li@intel.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	 Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Ori Kam <orika@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd: Document what the application does.
Date: Mon, 13 Sep 2021 17:28:50 -0700	[thread overview]
Message-ID: <CACZ4nhsF5v61Mi=E5YBUbbh2VFX68pP_f=MWOSzER2c55Xcqxg@mail.gmail.com> (raw)
In-Reply-To: <CACZ4nhtFCP0hTkpiB2BDPiKr2HLUtmTKRUYkqdsqum8in1guTQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2020 bytes --]

On Mon, Sep 13, 2021 at 5:26 PM Ajit Khaparde
<ajit.khaparde@broadcom.com> wrote:
>
> On Mon, Sep 13, 2021 at 11:59 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> >
> > 13/09/2021 20:33, Ben Pfaff:
> > > I could not find anything in the documentation that says what
> > > testpmd does.  This should save other people time trying to
> > > figure that out in the future.
> > >
> > > Signed-off-by: Ben Pfaff <blp@ovn.org>
> > [...]
> > > --- a/doc/guides/testpmd_app_ug/intro.rst
> > > +++ b/doc/guides/testpmd_app_ug/intro.rst
> > > @@ -6,9 +6,13 @@ Introduction
> > >
> > >  This document is a user guide for the ``testpmd`` example application that is shipped as part of the Data Plane Development Kit.
> > >
> > > -The ``testpmd`` application can be used to test the DPDK in a packet forwarding mode
> > > -and also to access NIC hardware features such as Flow Director.
> > > -It also serves as a example of how to build a more fully-featured application using the DPDK SDK.
> > > +``testpmd`` is a tool to test ethdev NIC features, including NIC
> > > +hardware features such as Flow Director.  It receives packets on each
> >
> > Not sure about keep mentioning Flow Director which is an Intel name
> > for an internal feature used through rte_flow rules.
> > What others think? Do we have better examples of hardware offload?
>
> We could use RSS and RFS.
> I think Receive Side Scaling and Receive Flow Steering would cover the
> intended offloads.
I forgot to mention RPS - Receive Packet Steering.

>
> >
> > > +configured port and forwards them.  By default, packets received on
> > > +port 0 are forwarded to port 1, and vice versa, and similarly for
> > > +ports 2 and 3, ports 4 and 5, and so on.  If an odd number of ports is
> > > +configured, packets received on the last port are sent back out on the
> > > +same port.
> > >
> > >  The guide shows how to build and run the testpmd application and
> > >  how to configure the application from the command line and the run-time environment.
> >
> >
> >

  reply	other threads:[~2021-09-14  0:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 18:33 Ben Pfaff
2021-09-13 18:58 ` Thomas Monjalon
2021-09-14  0:26   ` Ajit Khaparde
2021-09-14  0:28     ` Ajit Khaparde [this message]
2021-09-14  8:08 ` Ferruh Yigit

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='CACZ4nhsF5v61Mi=E5YBUbbh2VFX68pP_f=MWOSzER2c55Xcqxg@mail.gmail.com' \
    --to=ajit.khaparde@broadcom.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=blp@ovn.org \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jerinj@marvell.com \
    --cc=orika@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=xiaoyun.li@intel.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).