From: Wei Ling <weix.ling@intel.com>
To: dts@dpdk.org
Cc: Wei Ling <weix.ling@intel.com>
Subject: [dts][PATCH V1 0/3] modify basic_4k_pages_cbdma by DPDK changed
Date: Mon, 5 Jun 2023 14:33:59 +0800 [thread overview]
Message-ID: <20230605063359.563731-1-weix.ling@intel.com> (raw)
As the DPDK commit a399d7b5(vfio: do not coalesce DMA mappings) changed,
We need to delete the `--no-huge -m 1024` parameter when start the
vhost-user as back-end side.
1.Delete the `--no-huge -m 1024` parameter in testplan.
2.Delete the `--no-huge -m 1024` parameter in testsuite and add handle
expected value in conf/basic_4k_pages_cbdma.cfg.
3.Add [suite] section to save case config and expected values.
Wei Ling (3):
test_plans/basic_4k_pages_cbdma: modify testplan by DPDK changed
tests/basic_4k_pages_cbdma: modify testsuite by DPDK changed
conf/basic_4k_pages_cbdma: add suite config as expected values
conf/basic_4k_pages_cbdma.cfg | 7 +
test_plans/basic_4k_pages_cbdma_test_plan.rst | 560 +++++++++---------
tests/TestSuite_basic_4k_pages_cbdma.py | 225 +++++--
3 files changed, 457 insertions(+), 335 deletions(-)
--
2.34.1
reply other threads:[~2023-06-05 6:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230605063359.563731-1-weix.ling@intel.com \
--to=weix.ling@intel.com \
--cc=dts@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 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).