From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Zhu, ShuaiX" <shuaix.zhu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhu, ShuaiX" <shuaix.zhu@intel.com>
Subject: Re: [dts] [PATCH V2] tests/vhost_virtio_user_interrupt:enable control queue.
Date: Wed, 27 Nov 2019 09:43:48 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB698B3@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1574847718-148815-1-git-send-email-shuaix.zhu@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhu,shuai
> Sent: Wednesday, November 27, 2019 5:42 PM
> To: dts@dpdk.org
> Cc: Zhu, ShuaiX <shuaix.zhu@intel.com>
> Subject: [dts] [PATCH V2] tests/vhost_virtio_user_interrupt:enable control
> queue.
>
> Add the 'cq=1' parameter to enable the control queue.
>
> Signed-off-by: zhu,shuai <shuaix.zhu@intel.com>
> ---
> tests/TestSuite_vhost_virtio_user_interrupt.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/TestSuite_vhost_virtio_user_interrupt.py
> b/tests/TestSuite_vhost_virtio_user_interrupt.py
> index 002588d..288da2b 100644
> --- a/tests/TestSuite_vhost_virtio_user_interrupt.py
> +++ b/tests/TestSuite_vhost_virtio_user_interrupt.py
> @@ -94,7 +94,7 @@ class TestVirtioUserInterrupt(TestCase):
> cmd_l3fwd = "./examples/l3fwd-power/build/l3fwd-power " + \
> "-n %d -c %s --socket-mem 1024,1024 --legacy-mem " + \
> "--log-level='user1,7' --no-pci --file-prefix=l3fwd-pwd " + \
> - "--vdev=virtio_user0,path=%s -- -p 1 " + \
> + "--vdev=virtio_user0,path=%s,cq=1 -- -p 1 " + \
> " -P --config='(0,0,%s)' --parse-ptype "
> cmd_l3fwd = cmd_l3fwd % (self.mem_channel, self.core_mask_l3fwd,
> path, self.core_interrupt)
> --
> 2.17.2
prev parent reply other threads:[~2019-11-27 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 9:41 zhu,shuai
2019-11-27 9:43 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BB698B3@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=shuaix.zhu@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).