From: Thomas Monjalon <thomas@monjalon.net>
To: Ben Pfaff <blp@ovn.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: Document what the application does.
Date: Fri, 10 Sep 2021 23:14:26 +0200 [thread overview]
Message-ID: <5977659.pG1F7i0IUM@thomas> (raw)
In-Reply-To: <20210910175733.1248739-1-blp@ovn.org>
10/09/2021 19:57, 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.
Good move indeed :)
> --- a/doc/guides/testpmd_app_ug/run_app.rst
> +++ b/doc/guides/testpmd_app_ug/run_app.rst
> @@ -15,6 +15,12 @@ a list of available EAL command-line options.
> Testpmd Command-line Options
> ----------------------------
>
> +By default, testpmd receives packets on each configured port and
> +forwards the received packets to its paired port. Ports 0 and 1 are
> +paired, as are ports 2 and 3, and so on. With an odd number of ports,
> +the last port is paired with itself: packets received on the port are
> +sent back out on the same port.
So the intent is to say what is the default behaviour?
We could also update the introduction which is outdated:
"
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.
"
The last sentence should be removed.
The first sentence is a bit outdated.
We should say "testpmd is a tool to test ethdev NIC features".
May I take the opportunity of this patch to improve this intro as well?
next prev parent reply other threads:[~2021-09-10 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 17:57 [dpdk-dev] [PATCH] app/testpmd: Document what the application does Ben Pfaff
2021-09-10 21:14 ` Thomas Monjalon [this message]
2021-09-13 18:25 ` Ben Pfaff
2021-09-14 7:58 ` Ferruh Yigit
2021-10-06 16:28 ` Ben Pfaff
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=5977659.pG1F7i0IUM@thomas \
--to=thomas@monjalon.net \
--cc=blp@ovn.org \
--cc=dev@dpdk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.