From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Ling, WeiX" <weix.ling@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "He, Xingguang" <xingguang.he@intel.com>,
"Ling, WeiX" <weix.ling@intel.com>
Subject: RE: [dts][PATCH V1 2/2] tests/vm2vm_virtio_user: Modify case sync with testplan
Date: Fri, 11 Feb 2022 06:02:56 +0000 [thread overview]
Message-ID: <d872ecef81e5497dba7ab0c6957d4e40@intel.com> (raw)
In-Reply-To: <20220210074729.3929646-2-weix.ling@intel.com>
> -----Original Message-----
> From: Wei Ling <weix.ling@intel.com>
> Sent: 2022年2月10日 15:47
> To: dts@dpdk.org
> Cc: He, Xingguang <xingguang.he@intel.com>; Ling, WeiX <weix.ling@intel.com>
> Subject: [dts][PATCH V1 2/2] tests/vm2vm_virtio_user: Modify case sync with
> testplan
>
> 1.To cover all paths, four cases related to split ring (test cases 14, 15, 16, 17)
> and four cases related to packed ring (test cases 20, 21, 22, 23) are added.
> 2.Cbdma related cases(case 12, 13, 18, 19), the iova = PA step is added.
> 3.Case 24: to test the indirect feature when choose packed vectorized-tx path,
> and we have no relevant cases before.
>
> Signed-off-by: Wei Ling <weix.ling@intel.com>
Series applied.
next prev parent reply other threads:[~2022-02-11 6:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 7:47 [dts][PATCH V1 1/2] test_plans/vm2vm_virtio_user: Modify test plan to coverage more test point Wei Ling
2022-02-10 7:47 ` [dts][PATCH V1 2/2] tests/vm2vm_virtio_user: Modify case sync with testplan Wei Ling
2022-02-11 3:42 ` He, Xingguang
2022-02-11 5:34 ` Jiang, YuX
2022-02-11 6:02 ` Tu, Lijuan [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-10 6:13 [dts][PATCH V1 1/2] test_plans/vm2vm_virtio_user: modify test plan to coverage more test point Lingli Chen
2022-02-10 6:13 ` [dts][PATCH V1 2/2] tests/vm2vm_virtio_user: Modify case sync with testplan Lingli Chen
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=d872ecef81e5497dba7ab0c6957d4e40@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=weix.ling@intel.com \
--cc=xingguang.he@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).