test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Jiang, YuX" <yux.jiang@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Jiang, YuX" <yux.jiang@intel.com>
Subject: Re: [dts] [PATCH V2 0/2] rxtx_offload: add test plan and tests for tx offload multi_segs setting
Date: Fri, 27 Aug 2021 08:25:12 +0000	[thread overview]
Message-ID: <2ff76909f06d4fc3b6fc99235f190f9d@intel.com> (raw)
In-Reply-To: <1629861108-30497-1-git-send-email-yux.jiang@intel.com>



> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Yu Jiang
> Sent: 2021年8月25日 11:12
> To: dts@dpdk.org
> Cc: Jiang, YuX <yux.jiang@intel.com>
> Subject: [dts] [PATCH V2 0/2] rxtx_offload: add test plan and tests for tx offload
> multi_segs setting
> 
> vector path doesn't support multi-segment packet transmit, only normal path
> supports multi-segment packet transmit.
> Use 'port config 0 tx_offload multi_segs on' or "--tx-offloads=0x00008000"
> parameter to enable multi segment offload.
> 
> Yu Jiang (2):
>   tests/rxtx_offload: add tx offload multi_segs setting case
>   test_plans/rxtx_offload: add tx offload multi_segs setting plan
> 
>  test_plans/rxtx_offload_test_plan.rst | 99
> +++++++++++++++++++++++++++++++++++
>  tests/TestSuite_rxtx_offload.py       | 66 +++++++++++++++++++++++
>  2 files changed, 165 insertions(+)

Applied, thanks
> 
> --
> 2.7.4


      parent reply	other threads:[~2021-08-27  8:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25  3:11 Yu Jiang
2021-08-25  3:11 ` [dts] [PATCH V2 1/2] tests/rxtx_offload: add tx offload multi_segs setting case Yu Jiang
2021-08-25  3:17   ` Jiang, YuX
2021-08-25  3:11 ` [dts] [PATCH V2 2/2] test_plans/rxtx_offload: add tx offload multi_segs setting plan Yu Jiang
2021-08-27  8:25 ` 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=2ff76909f06d4fc3b6fc99235f190f9d@intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=yux.jiang@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).