From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Vipin Varghese <vipin.varghese@intel.com>, dev@dpdk.org
Cc: pascal.mazon@6wind.com
Subject: Re: [dpdk-dev] [PATCH] test/tun: add new test for tun
Date: Tue, 17 Apr 2018 19:02:29 +0100 [thread overview]
Message-ID: <f5572c86-1920-e59a-95c2-c8a5b8336714@intel.com> (raw)
In-Reply-To: <1522917075-5156-1-git-send-email-vipin.varghese@intel.com>
On 4/5/2018 9:31 AM, Vipin Varghese wrote:
> Add TUN PMD validation for create, port setup, tx, rx and stats functions.
>
> Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
> ---
> test/test/Makefile | 4 +
> test/test/autotest_data.py | 13 ++
> test/test/meson.build | 4 +
> test/test/test_tun.c | 333 +++++++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 354 insertions(+)
> create mode 100644 test/test/test_tun.c
>
> diff --git a/test/test/Makefile b/test/test/Makefile
> index a88cc38..e5d8200 100644
> --- a/test/test/Makefile
> +++ b/test/test/Makefile
> @@ -193,6 +193,10 @@ endif
>
> SRCS-$(CONFIG_RTE_LIBRTE_KVARGS) += test_kvargs.c
>
> +ifeq ($(CONFIG_RTE_LIBRTE_PMD_TAP),y)
> +SRCS-y += test_tun.c
> +endif
> +
> CFLAGS += -DALLOW_EXPERIMENTAL_API
>
> CFLAGS += -O3
> diff --git a/test/test/autotest_data.py b/test/test/autotest_data.py
> index aacfe0a..35f3aab 100644
> --- a/test/test/autotest_data.py
> +++ b/test/test/autotest_data.py
> @@ -357,6 +357,19 @@ def per_sockets(num):
> ]
> },
> {
> + "Prefix": "tun",
> + "Memory": "512",
> + "Tests":
> + [
> + {
> + "Name": "TUN autotest",
> + "Command": "tun_autotest",
> + "Func": default_autotest,
> + "Report": None,
> + },
> + ]
> + },
> + {
Hi Vipin,
Thanks for providing unit test for the feature you have added. *I believe we
need more unit test in DPDK.*
Only a few questions:
1- Should this be part of auto test?
2- Second running of the tun_autotest is failing, exit test and re-run works,
any idea?
Overall I am for merging this unit test if there is no objection.
Thanks,
ferruh
next prev parent reply other threads:[~2018-04-17 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 8:31 Vipin Varghese
2018-04-17 18:02 ` Ferruh Yigit [this message]
2018-04-19 3:39 ` Varghese, Vipin
2018-05-22 20:39 ` Ferruh Yigit
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=f5572c86-1920-e59a-95c2-c8a5b8336714@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=pascal.mazon@6wind.com \
--cc=vipin.varghese@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).