test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Wang, Yinan" <yinan.wang@intel.com>
To: "Min, JiaqiX" <jiaqix.min@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Min, JiaqiX" <jiaqix.min@intel.com>
Subject: Re: [dts] [PATCH v1] test_plans/vf_interrupt_pmd: add fvl multi queue	interrupt
Date: Wed, 19 Feb 2020 08:27:26 +0000	[thread overview]
Message-ID: <a886a8492589453796d12066fb61c3b9@intel.com> (raw)
In-Reply-To: <20200213102029.142256-1-jiaqix.min@intel.com>

Acked-by: Wang, Yinan <yinan.wang@intel.com>

> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Jiaqi Min
> Sent: 2020年2月13日 18:20
> To: dts@dpdk.org
> Cc: Min, JiaqiX <jiaqix.min@intel.com>
> Subject: [dts] [PATCH v1] test_plans/vf_interrupt_pmd: add fvl multi queue
> interrupt
> 
> add multi queue interrupt for fvl
> 
> Signed-off-by: Jiaqi Min <jiaqix.min@intel.com>
> ---
>  test_plans/vf_interrupt_pmd_test_plan.rst | 35 ++++++++++++++++++++++-
>  1 file changed, 34 insertions(+), 1 deletion(-)
> 
> diff --git a/test_plans/vf_interrupt_pmd_test_plan.rst
> b/test_plans/vf_interrupt_pmd_test_plan.rst
> index 8f91b14..db05cb4 100644
> --- a/test_plans/vf_interrupt_pmd_test_plan.rst
> +++ b/test_plans/vf_interrupt_pmd_test_plan.rst
> @@ -190,4 +190,37 @@ Test Case4: VF interrupt pmd in VM with vfio-pci
> 
>  7. Check if threads on core 2 have returned to sleep mode::
> 
> -    L3FWD_POWER: lcore 2 sleeps until interrupt triggers
> \ No newline at end of file
> +    L3FWD_POWER: lcore 2 sleeps until interrupt triggers
> +
> +Test Case5: Check Interrupt for VF with 4 queues and vfio driver on
> +i40e
> +===============================================================
> ========
> +=
> +
> +1. Generate NIC VF, then bind it to vfio drvier::
> +
> +    echo 1 > /sys/bus/pci/devices/0000\:04\:00.0/sriov_numvfs
> +
> +    modprobe vfio-pci
> +    usertools/dpdk-devbind.py --bind=vfio-pci 0000:04:10.0(vf_pci)
> +
> +  Notice:  If your PF is kernel driver, make sure PF link is up when your start
> testpmd on VF.
> +
> +2. Start l3fwd-power with VF::
> +
> +    examples/l3fwd-power/build/l3fwd-power -c 3f -n 4 -m 2048 -- -P -p 0x1
> --config="(0,0,1),(0,1,2),(0,2,3),(0,3,4)"
> +
> +3. Send packet with packet generator to the pf NIC, check that all threads
> waked up::
> +
> +    for x in range(0,10):
> +     sendp([Ether(dst='vf_mac')/IP(src='2.1.1.' +
> + str(x),dst='2.1.1.5')/UDP()/Raw(load='XXXXXXXXXXXXXXXXXX')],
> + iface="tester_intf")
> +
> +    L3FWD_POWER: lcore 1 is waked up from rx interrupt on port 0 queue 0
> +    L3FWD_POWER: lcore 2 is waked up from rx interrupt on port 0 queue 1
> +    L3FWD_POWER: lcore 3 is waked up from rx interrupt on port 0 queue 2
> +    L3FWD_POWER: lcore 4 is waked up from rx interrupt on port 0 queue
> + 3
> +
> +4. Check if threads on all cores have returned to sleep mode::
> +
> +    L3FWD_POWER: lcore 1 sleeps until interrupt triggers
> +    L3FWD_POWER: lcore 2 sleeps until interrupt triggers
> +    L3FWD_POWER: lcore 3 sleeps until interrupt triggers
> +    L3FWD_POWER: lcore 4 sleeps until interrupt triggers
> --
> 2.17.1


      reply	other threads:[~2020-02-19  8:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 10:20 Jiaqi Min
2020-02-19  8:27 ` Wang, Yinan [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=a886a8492589453796d12066fb61c3b9@intel.com \
    --to=yinan.wang@intel.com \
    --cc=dts@dpdk.org \
    --cc=jiaqix.min@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).