test suite reviews and discussions
 help / color / mirror / Atom feed
From: Rami Rosen <ramirose@gmail.com>
To: xuyanjie <yanjie.xu@intel.com>
Cc: dts@dpdk.org
Subject: Re: [dts] [PATCH] add iavf test plan
Date: Tue, 16 Apr 2019 22:28:23 +0300	[thread overview]
Message-ID: <CAHLOa7QRkyqppTViV7NAx4z4n+87bLXttZ-1RPsyfkD6E96mVA@mail.gmail.com> (raw)
In-Reply-To: <1555431074-168977-1-git-send-email-yanjie.xu@intel.com>

[-- Attachment #1: Type: text/plain, Size: 853 bytes --]

>
>
>
> +Test Cases:  Rx interrupt
> +====================================================================
> +
> +Test case: rx interrupt
> +
>

[Rami]  no need for two build commands in the following line:

+1. build build l3fwd power
> +    make -C examples/l3fwd-power RTE_SDK=`pwd`
> T=x86_64-native-linuxapp-gcc
> +
> +2. build two VFs with igb_uio
> +   modprobe uio;
> +   insmod x86_64-native-linuxapp-gcc/kmod/igb_uio.ko;
> +   # ./usertools/dpdk-devbind.py --bind=igb_uio 18:02.0 18:0a.0
> +
>
...
...

[Rami] vefify-> verify

+    send traffic and vefify throughput
> +
> +Test Csse: scalar/bulk vf performance
> +
> +1. change CONFIG_RTE_LIBRTE_AVF_INC_VECTOR=n in config/common_base, and
> rebuild dpdk
> +
> +2. repeat test steps 2-4 in above test case: vector vf performance.
> \ No newline at end of file
> --
>

>
> Regards,
Rami Rosen

[-- Attachment #2: Type: text/html, Size: 2459 bytes --]

  parent reply	other threads:[~2019-04-16 19:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 16:11 xuyanjie
2019-04-16 18:07 ` Tu, Lijuan
2019-04-16 19:28 ` Rami Rosen [this message]
2019-04-17  2:30 ` Lin, Xueqin
2019-04-17  8:53 xuyanjie
2019-04-23 21:05 ` 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=CAHLOa7QRkyqppTViV7NAx4z4n+87bLXttZ-1RPsyfkD6E96mVA@mail.gmail.com \
    --to=ramirose@gmail.com \
    --cc=dts@dpdk.org \
    --cc=yanjie.xu@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).