DPDK usage discussions
 help / color / mirror / Atom feed
From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: Changchun Zhang <changchun.zhang@oracle.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Guide on DPDK test command
Date: Tue, 26 Feb 2019 11:28:01 +0000	[thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435896F7EB7@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <bf0b15f3-5219-4396-a78e-8bec4769134b@default>

Hi

> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Changchun Zhang
> Sent: Monday, February 25, 2019 11:58 PM
> To: users@dpdk.org
> Subject: [dpdk-users] Guide on DPDK test command
> 
> Hi Gurus,
> 
> 
> 
> It is seen that the dpdk provides unit test tool for many dpdk functionality, in the folder test/, like
> test_crytodev.c. These files contain the callback functions and the data structures for test command.
> 
> Does any guy know how to use these test functions and is there any guides?
[Fiona] I don't know of a guide, but what I do is:
set up hugepages, e.g. by using ./usertools/dpdk-setup.sh
make test-build -j
cd build/app
./test -n1 -l2
>crypto... (tab will autocomplete and you can see which test suites are available, e.g. cryptodev_null_autotest will run on the NULL pmd)

For most other PMDs which depend on external libs you'll need to ensure you have the lib installed on your platform. And enable the build in the config file. Instructions specific to each PMD are here:
http://doc.dpdk.org/guides/cryptodevs/index.html

           reply	other threads:[~2019-02-26 11:28 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bf0b15f3-5219-4396-a78e-8bec4769134b@default>]

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=348A99DA5F5B7549AA880327E580B435896F7EB7@IRSMSX101.ger.corp.intel.com \
    --to=fiona.trahe@intel.com \
    --cc=changchun.zhang@oracle.com \
    --cc=users@dpdk.org \
    /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).