test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Xiao, QimaiX" <qimaix.xiao@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1]test_plans/vhost_enqueue_interrupt_test_plan: remove old testplan
Date: Wed, 2 Sep 2020 02:18:32 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0C65693A@SHSMSX107.ccr.corp.intel.com> (raw)
In-Reply-To: <MWHPR1101MB22542B4F21E7B20A8041A50BFB550@MWHPR1101MB2254.namprd11.prod.outlook.com>

test_plans/vhost_enqueue_interrupt_test_plan.rst: does not exist

> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Xiao, QimaiX
> Sent: 2020年8月27日 18:13
> To: dts@dpdk.org
> Subject: Re: [dts] [PATCH V1]test_plans/vhost_enqueue_interrupt_test_plan:
> remove old testplan
> 
> Tested-by: Xiao Qimai <qimaix.xiao@intel.com>
> 
> Regards,
> Xiao Qimai
> 
> > -----Original Message-----
> > From: Xiao, QimaiX <qimaix.xiao@intel.com>
> > Sent: Thursday, August 27, 2020 5:41 PM
> > To: dts@dpdk.org
> > Cc: Xiao, QimaiX <qimaix.xiao@intel.com>
> > Subject: [dts][PATCH V1]test_plans/vhost_enqueue_interrupt_test_plan:
> > remove old testplan
> >
> > *. test_plans/vhost_enqueue_interrupt_test_plan has been replaced by
> > test_plans/vhost_user_interrupt_test_plan.rst
> >
> > Signed-off-by: Xiao Qimai <qimaix.xiao@intel.com>
> > ---
> >  .../vhost_enqueue_interrupt_test_plan.rst     | 145 ------------------
> >  1 file changed, 145 deletions(-)
> >  delete mode 100644 test_plans/vhost_enqueue_interrupt_test_plan.rst
> >
> > diff --git a/test_plans/vhost_enqueue_interrupt_test_plan.rst
> > b/test_plans/vhost_enqueue_interrupt_test_plan.rst
> > deleted file mode 100644
> > index ee9b7a5d..00000000
> > --- a/test_plans/vhost_enqueue_interrupt_test_plan.rst
> > +++ /dev/null
> > @@ -1,145 +0,0 @@
> > -.. Copyright (c) <2019>, Intel Corporation
> > -   All rights reserved.
> > -
> > -   Redistribution and use in source and binary forms, with or without
> > -   modification, are permitted provided that the following conditions
> > -   are met:
> > -
> > -   - Redistributions of source code must retain the above copyright
> > -     notice, this list of conditions and the following disclaimer.
> > -
> > -   - Redistributions in binary form must reproduce the above copyright
> > -     notice, this list of conditions and the following disclaimer in
> > -     the documentation and/or other materials provided with the
> > -     distribution.
> > -
> > -   - Neither the name of Intel Corporation nor the names of its
> > -     contributors may be used to endorse or promote products derived
> > -     from this software without specific prior written permission.
> > -
> > -   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
> > CONTRIBUTORS
> > -   "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
> > NOT
> > -   LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
> > FITNESS
> > -   FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
> > -   COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
> > INDIRECT,
> > -   INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> > -   (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
> > GOODS OR
> > -   SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
> > -   HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
> > CONTRACT,
> > -   STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
> > -   ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
> > ADVISED
> > -   OF THE POSSIBILITY OF SUCH DAMAGE.
> > -
> > -======================================
> > -vhost enqueue interrupt mode test plan
> > -======================================
> > -
> > -Description
> > -===========
> > -
> > -Vhost enqueue interrupt need test with l3fwd-power sample, small
> > packets send from virtio-user to vhost side,
> > -check vhost-user cores can be wakeup,and vhost-user cores should be
> > back to sleep after stop sending packets -from virtio side.
> > -
> > -Prerequisites
> > -=============
> > -
> > -Modify l3fwd-power example code and recompile::
> > -
> > -        --- a/examples/l3fwd-power/main.c
> > -        +++ b/examples/l3fwd-power/main.c
> > -        @@ -248,7 +248,6 @@ static struct rte_eth_conf port_conf = {
> > -                .mq_mode        = ETH_MQ_RX_RSS,
> > -                .max_rx_pkt_len = RTE_ETHER_MAX_LEN,
> > -                .split_hdr_size = 0,
> > -        -       .offloads = DEV_RX_OFFLOAD_CHECKSUM,
> > -        },
> > -        .rx_adv_conf = {
> > -                .rss_conf = {
> > -
> > -Test flow
> > -=========
> > -
> > -Virtio-user --> Vhost-user
> > -
> > -Test Case1: Wake up split ring vhost-user core with l3fwd-power
> > sample -
> ==========================================================
> > ============
> > -
> > -1. Launch virtio-user with server mode::
> > -
> > -    ./testpmd -l 7-8 -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci --file-
> > prefix=virtio \
> > -    --
> > vdev=net_virtio_user0,mac=00:11:22:33:44:10,path=/tmp/sock0,server=1,q
> > u
> > eues=1 -- -i
> > -
> > -2. Build l3fwd-power sample and launch l3fwd-power with a virtual
> > vhost
> > device::
> > -
> > -    ./l3fwd-power -l 0-3 -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci \
> > -    --vdev 'eth_vhost0,iface=/tmp/sock0,queues=1,client=1' -- -p 0x1 --parse-
> > ptype 1 --config "(0,0,2)"
> > -
> > -3. Send packet by testpmd, check vhost-user core will keep wakeup status::
> > -
> > -    testpmd>set fwd txonly
> > -    testpmd>start
> > -
> > -4. Stop and restart testpmd again, check vhost-user core will sleep
> > and wakeup again.
> > -
> > -Test Case2: Wake up split ring vhost-user cores with l3fwd-power
> > sample when multi queues are enabled -
> > ==========================================================
> > ===========================================
> > -
> > -1. Launch virtio-user with server mode::
> > -
> > -    ./testpmd -l 1-5 -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci --file-
> > prefix=virtio \
> > -    --
> > vdev=net_virtio_user0,mac=00:11:22:33:44:10,path=/tmp/sock0,server=1,q
> > u
> > eues=4 -- -i --rxq=4 --txq=4 --rss-ip
> > -
> > -2. Build l3fwd-power sample and launch l3fwd-power with a virtual
> > vhost
> > device::
> > -
> > -    ./l3fwd-power -l 9-12 -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci
> > --log-level=9 \
> > -    --vdev 'eth_vhost0,iface=/tmp/sock0,queues=4,client=1' -- -p 0x1 --parse-
> > ptype 1 \
> > -    --config "(0,0,9),(0,1,10),(0,2,11),(0,3,12)"
> > -
> > -3. Send packet by testpmd, check vhost-user multi-cores will keep
> > wakeup
> > status::
> > -
> > -    testpmd>set fwd txonly
> > -    testpmd>start
> > -
> > -4. Stop and restart testpmd again, check vhost-user cores will sleep
> > and wakeup again.
> > -
> > -Test Case3: Wake up packed ring vhost-user core with l3fwd-power
> > sample -
> ==========================================================
> > =============
> > -
> > -1. Launch virtio-user with server mode::
> > -
> > -    ./testpmd -l 7-8 -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci --file-
> > prefix=virtio \
> > -    --
> > vdev=net_virtio_user0,mac=00:11:22:33:44:10,path=/tmp/sock0,server=1,q
> > u
> > eues=1,packed_vq=1 -- -i
> > -
> > -2. Build l3fwd-power sample and launch l3fwd-power with a virtual
> > vhost
> > device::
> > -
> > -    ./l3fwd-power -l 0-3 -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci \
> > -    --vdev 'eth_vhost0,iface=/tmp/sock0,queues=1,client=1' -- -p 0x1 --parse-
> > ptype 1 --config "(0,0,2)"
> > -
> > -3. Send packet by testpmd, check vhost-user core will keep wakeup status::
> > -
> > -    testpmd>set fwd txonly
> > -    testpmd>start
> > -
> > -4. Stop and restart testpmd again, check vhost-user core will sleep
> > and wakeup again.
> > -
> > -Test Case4:  Wake up packed ring vhost-user cores with l3fwd-power
> > sample when multi queues are enabled -
> > ==========================================================
> > =============================================
> > -
> > -1. Launch virtio-user with server mode::
> > -
> > -    ./testpmd -l 1-5 -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci --file-
> > prefix=virtio \
> > -    --
> > vdev=net_virtio_user0,mac=00:11:22:33:44:10,path=/tmp/sock0,server=1,q
> > u
> > eues=4,packed_vq=1,mrg_rxbuf=0 -- -i --rxq=4 --txq=4 --rss-ip
> > -
> > -2. Build l3fwd-power sample and launch l3fwd-power with a virtual
> > vhost
> > device::
> > -
> > -    ./l3fwd-power -l 9-12 -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci
> > --log-level=9 \
> > -    --vdev 'eth_vhost0,iface=/tmp/sock0,queues=4,client=1' -- -p 0x1 --parse-
> > ptype 1 \
> > -    --config "(0,0,9),(0,1,10),(0,2,11),(0,3,12)"
> > -
> > -3. Send packet by testpmd, check vhost-user multi-cores will keep
> > wakeup
> > status::
> > -
> > -    testpmd>set fwd txonly
> > -    testpmd>start
> > -
> > -4. Stop and restart testpmd again, check vhost-user cores will sleep
> > and wakeup again.
> > --
> > 2.25.1


  reply	other threads:[~2020-09-02  2:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27  9:41 Xiao Qimai
2020-08-27 10:13 ` Xiao, QimaiX
2020-09-02  2:18   ` Tu, Lijuan [this message]
2020-09-02  3:02     ` Tu, Lijuan

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=8CE3E05A3F976642AAB0F4675D0AD20E0C65693A@SHSMSX107.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=qimaix.xiao@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).