From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Agalya Babu RadhaKrishnan <agalyax.babu.radhakrishnan@intel.com>,
dev@dpdk.org
Cc: reshma.pattan@intel.com, olivier.matz@6wind.com,
bernard.iremonger@intel.com
Subject: Re: [dpdk-dev] [PATCH] doc: fix interactive commands in testpmd guide
Date: Tue, 16 Apr 2019 16:05:30 +0100 [thread overview]
Message-ID: <21bf3efc-dd06-6a33-a88f-c5b1cf93f6a6@intel.com> (raw)
Message-ID: <20190416150530.sD7uanwk11HjY6UDzCwI3qTM1MVBvuPWgQ2rjT9XDbA@z> (raw)
In-Reply-To: <1555396398-17880-1-git-send-email-agalyax.babu.radhakrishnan@intel.com>
On 4/16/2019 7:33 AM, Agalya Babu RadhaKrishnan wrote:
> From: Agalya Babu RadhaKrishnan <agalyax.babu.radhakrishnan@intel.com>
>
> Added some missing documentation for interactive mode commands
>
> Fixes: 01b2092a5e ("testpmd: add dump commands for debug")
> Fixes: caf05a1b86 ("app/testpmd: new command to dump log types")
>
> Signed-off-by: Agalya Babu RadhaKrishnan <agalyax.babu.radhakrishnan@intel.com>
Hi Agalya,
Good to see the documentation is updated to cover the gaps, this patch documents
various commands, are above fixes lines cover all commits?
> ---
> doc/guides/testpmd_app_ug/testpmd_funcs.rst | 101 ++++++++++++++++++++
> 1 file changed, 101 insertions(+)
>
> diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
> index 5d4dc6f0c..a8954c279 100644
> --- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
> +++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
> @@ -467,6 +467,57 @@ Show Tx metadata value set for a specific port::
>
> testpmd> show port (port_id) tx_metadata
>
> +dump physmem
> +~~~~~~~~~~~~
> +
> +Dumps all physical memory segment layouts::
> +
> + testpmd> dump_physmem
> +
> +dump memzone
> +~~~~~~~~~~~~
> +
> +Dumps the layout of all memory zones::
> +
> + testpmd> dump_memzone
> +
> +
> +dump struct size
> +~~~~~~~~~~~~~~~~
> +
> +Dumps the size of all memory structures::
> +
> + testpmd> dump_struct_sizes
> +
> +dump ring
> +~~~~~~~~~
> +
> +Dumps the status of all or specific element in DPDK rings::
> +
> + testpmd> dump_ring (string)
> +
> +dump mempool
> +~~~~~~~~~~~~
> +
> +Dumps the statistics of all or specific memory pool::
> +
> + testpmd> dump_mempool (string)
> + testpmd> dump_mempool (name)
> +
> +dump devargs
> +~~~~~~~~~~~~
> +
> +Dumps the user device list::
> +
> + testpmd> dump_devargs
> +
> +dump log types
> +~~~~~~~~~~~~~~
> +
> +Dumps the log level for all the dpdk modules::
> +
> + testpmd> dump_log_types
> +
> Configuration Functions
> -----------------------
>
> @@ -1041,6 +1092,20 @@ Display the status of TCP Segmentation Offload::
>
> testpmd> tso show (port_id)
>
> +tunnel tso set
> +~~~~~~~~~~~~~~
> +
> +Set tso segment size of tunneled packets for a port in csum engine::
> +
> + testpmd> tunnel_tso set (tso_segsz) (port_id)
> +
> +tunnel tso show
> +~~~~~~~~~~~~~~~
> +
> +Display the status of tunneled TCP Segmentation Offload for a port::
> +
> + testpmd> tunnel_tso show (port_id)
> +
> set port - gro
> ~~~~~~~~~~~~~~
>
> @@ -1162,6 +1227,22 @@ Remove a MAC address from a port::
>
> testpmd> mac_addr remove (port_id) (XX:XX:XX:XX:XX:XX)
>
> +mcast_addr add
> +~~~~~~~~~~~~~~
> +
> +To add the multicast MAC address to/from the set of multicast addresses
> +filtered by port::
> +
> + testpmd> mcast_addr add (port_id) (mcast_addr)
> +
> +mcast_addr remove
> +~~~~~~~~~~~~~~~~~
> +
> +To remove the multicast MAC address to/from the set of multicast addresses
> +filtered by port::
> +
> + testpmd> mcast_addr remove (port_id) (mcast_addr)
> +
> mac_addr add (for VF)
> ~~~~~~~~~~~~~~~~~~~~~
>
> @@ -2183,6 +2264,26 @@ testpmd will add this value to any Tx packet sent from this port::
>
> testpmd> port config (port_id) tx_metadata (value)
>
> +port config mtu
> +~~~~~~~~~~~~~~~
> +
> +To configure MTU(Maximum Transmission Unit) on devices using testpmd::
> +
> + testpmd> port config mtu (port_id) (value)
> +
> +port config rss hash key
> +~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +To configure the RSS hash key used to compute the RSS
> +hash of input [IP] packets received on port::
> +
> + testpmd> port config <port_id> rss-hash-key (ipv4|ipv4-frag|\
> + ipv4-tcp|ipv4-udp|ipv4-sctp|ipv4-other|\
> + ipv6|ipv6-frag|ipv6-tcp|ipv6-udp|ipv6-sctp|\
> + ipv6-other|l2-payload|ipv6-ex|ipv6-tcp-ex|\
> + ipv6-udp-ex <string of hex digits \
> + (variable length, NIC dependent)>)
> +
> Link Bonding Functions
> ----------------------
>
>
next prev parent reply other threads:[~2019-04-16 15:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 6:33 Agalya Babu RadhaKrishnan
2019-04-16 6:33 ` Agalya Babu RadhaKrishnan
2019-04-16 7:32 ` Rami Rosen
2019-04-16 7:32 ` Rami Rosen
2019-04-16 15:05 ` Ferruh Yigit [this message]
2019-04-16 15:05 ` Ferruh Yigit
2019-04-17 9:25 ` Iremonger, Bernard
2019-04-17 9:25 ` Iremonger, Bernard
2019-04-18 19:51 ` Ferruh Yigit
2019-04-18 19:51 ` Ferruh Yigit
2019-04-23 10:44 ` [dpdk-dev] [PATCH v2] " Agalya Babu RadhaKrishnan
2019-04-23 10:44 ` Agalya Babu RadhaKrishnan
2019-04-23 11:38 ` Ferruh Yigit
2019-04-23 11:38 ` 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=21bf3efc-dd06-6a33-a88f-c5b1cf93f6a6@intel.com \
--to=ferruh.yigit@intel.com \
--cc=agalyax.babu.radhakrishnan@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=reshma.pattan@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).