From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Lin, Xueqin" <xueqin.lin@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Lin, Xueqin" <xueqin.lin@intel.com>
Subject: Re: [dts] [PATCH 1/3] test_plan/shutdown_api: add rx/tx descriptor status test plan
Date: Wed, 6 May 2020 03:13:23 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC21D5C@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1588047409-91262-1-git-send-email-xueqin.lin@intel.com>
Applied the series, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Xueqin Lin
> Sent: Tuesday, April 28, 2020 12:17 PM
> To: dts@dpdk.org
> Cc: Lin, Xueqin <xueqin.lin@intel.com>
> Subject: [dts] [PATCH 1/3] test_plan/shutdown_api: add rx/tx descriptor
> status test plan
>
> Signed-off-by: Xueqin Lin <xueqin.lin@intel.com>
>
> ---
> test_plans/shutdown_api_test_plan.rst | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/test_plans/shutdown_api_test_plan.rst
> b/test_plans/shutdown_api_test_plan.rst
> index 83a495a..f92b08f 100644
> --- a/test_plans/shutdown_api_test_plan.rst
> +++ b/test_plans/shutdown_api_test_plan.rst
> @@ -245,3 +245,12 @@ Test Case: link stats 7. Run ``set link-up port X`` to
> set all port link up 8. Start packet generator to transmit and receive packets
> successfully.
> +
> +Test Case: RX/TX descriptor status
> +----------------------------------
> +
> +1. Lauch testpmd with rx/tx queue number ``--txq=16 --rxq=16`` and
> +rx/tx descriptor size ``--txd=4096 --rxd=4096`` 2. Run ``show port 0 rxq *
> desc * status`` to check rx descriptor status.
> +3. Check rx descriptor status can be ``AVAILABLE``, ``DONE`` or
> ``UNAVAILABLE``.
> +4. Run ``show port 0 txq * desc * status`` to check tx descriptor status.
> +5. Check tx descriptor status can be ``FULL``, ``DONE`` or ``UNAVAILABLE``.
> --
> 2.7.5
prev parent reply other threads:[~2020-05-06 3:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 4:16 Xueqin Lin
2020-05-06 3:13 ` Tu, Lijuan [this message]
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=8CE3E05A3F976642AAB0F4675D0AD20E0BC21D5C@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=xueqin.lin@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).