From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id D3121A04C5; Fri, 4 Sep 2020 02:32:34 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 6E3821C055; Fri, 4 Sep 2020 02:32:34 +0200 (CEST) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 8B541DE0 for ; Fri, 4 Sep 2020 02:32:32 +0200 (CEST) IronPort-SDR: Om5S6xdEt38kFoAJhyVUSSEaxrpreM58wrjFONJBAyFcWuZ9fRp93fE73WmsYmZVscvuurs1Aw umpE5EKMuE1w== X-IronPort-AV: E=McAfee;i="6000,8403,9733"; a="137728027" X-IronPort-AV: E=Sophos;i="5.76,387,1592895600"; d="scan'208";a="137728027" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Sep 2020 17:32:31 -0700 IronPort-SDR: 1/eQdap0ItJL0mj38KY1CMVAZIrNc9D24ZrD7EPyhdnGceJjsdLXenkHmjbgkhVbLHO6Jlxibb aTzsy/aCYncw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.76,387,1592895600"; d="scan'208";a="282854157" Received: from orsmsx601.amr.corp.intel.com ([10.22.229.14]) by fmsmga007.fm.intel.com with ESMTP; 03 Sep 2020 17:32:31 -0700 Received: from orsmsx607.amr.corp.intel.com (10.22.229.20) by ORSMSX601.amr.corp.intel.com (10.22.229.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Thu, 3 Sep 2020 17:32:30 -0700 Received: from orsmsx604.amr.corp.intel.com (10.22.229.17) by ORSMSX607.amr.corp.intel.com (10.22.229.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Thu, 3 Sep 2020 17:32:30 -0700 Received: from ORSEDG601.ED.cps.intel.com (10.7.248.6) by orsmsx604.amr.corp.intel.com (10.22.229.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5 via Frontend Transport; Thu, 3 Sep 2020 17:32:30 -0700 Received: from NAM04-SN1-obe.outbound.protection.outlook.com (104.47.44.52) by edgegateway.intel.com (134.134.137.102) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1713.5; Thu, 3 Sep 2020 17:32:29 -0700 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CKsNcrmmKH0+6CLnAp8GTVbm5PUUt+gZgTBcG0iN1wPTyQ3S5I2zJ1R3uWYzZACx3hQN4LGnI8HvjB5RP6LMeA2mqHL+F7AFZ/8SIBWOAPYbcYQa2G+ovV5IvWLrLiet/Zr0pjddmOWgkY3uhoC1/0DmAcjcxGiWpatoptvc4y088xNwI/uFJOWXMrdxdt1KS9MtcoBDuftUO10jDp2s2u6k/cjlmU/AkgO3wETtWoLImZlbe3bpZJ3metGVTZG5AppHTBpqX3/aiAZ6NDZXToLnTg+ui66rTOpezfEM/rVju7glx66oZf65UQMypVtuV+oMzPqN7eAdBoetyi6jLw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=scUynLk5ADVSJrs+mZb6LYkJj2wX29YNjLK7RicHqJ4=; b=V1rB0dRBkj6dlA2t6djt+dUTl7pkkWbjVCpKd/oZRmtDhy7nihNaK6u3zvPtZK4OBMsG1U5eSur8Yo43EjPeKuNgKMx5CEFISImE6H0hUtBs5wHWUj2v8QitJqkRnJVBUUfSiDiCpxNj4K+2KcxRpTAay7ROfWqE8TKk0WU7bh3BxtLKqHqCBCVbdFO7rfZ6xSr1h5J8Z+jRqUmdIUP6ivaFHN5ZEdWH62NU9Qopn+buSRmiIIGY6n48v9TF7U4erlrO+d1bpyNkwSB2FOa+YnkWkVx61wayxwjt0h4mN4/q1ClGqIbiGFCs6/Cmzqf8LUuKbbw8s/2qXhvVxs6gkQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=intel.com; dmarc=pass action=none header.from=intel.com; dkim=pass header.d=intel.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel.onmicrosoft.com; s=selector2-intel-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=scUynLk5ADVSJrs+mZb6LYkJj2wX29YNjLK7RicHqJ4=; b=k2aJIVFVxZYgwURYVFI8DQO7k2tHYD0k7oc1GxBy5fXZ2h2ILJnoyR3u9xtthoZFR4IDkiKDSpODRh394YwqPMC+8YlMTdVMH9f5LWlJUvho2BhwqPTpDlXo9tb/NmbUbJQDYFrlCuHQoiEQ6i9pZC7oERIgMENrexSEvcLNZ4s= Received: from BY5PR11MB4451.namprd11.prod.outlook.com (2603:10b6:a03:1cb::30) by BYAPR11MB3016.namprd11.prod.outlook.com (2603:10b6:a03:81::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3348.15; Fri, 4 Sep 2020 00:32:25 +0000 Received: from BY5PR11MB4451.namprd11.prod.outlook.com ([fe80::4162:97e1:7d04:a508]) by BY5PR11MB4451.namprd11.prod.outlook.com ([fe80::4162:97e1:7d04:a508%7]) with mapi id 15.20.3348.016; Fri, 4 Sep 2020 00:32:25 +0000 From: "Chautru, Nicolas" To: "Power, Ciara" , "dev@dpdk.org" CC: "Mcnamara, John" , "Kovacevic, Marko" , "Doherty, Declan" , "Pattan, Reshma" , "Tahhan, Maryam" , Jerin Jacob Thread-Topic: [PATCH v3 35/37] doc: remove reference to make in tools guides Thread-Index: AQHWggcZG+rC1ywwYEONqYB/vM76XKlXoFvw Date: Fri, 4 Sep 2020 00:32:24 +0000 Message-ID: References: <20200807123009.21266-1-ciara.power@intel.com> <20200903152717.42095-1-ciara.power@intel.com> <20200903152717.42095-36-ciara.power@intel.com> In-Reply-To: <20200903152717.42095-36-ciara.power@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-reaction: no-action dlp-version: 11.5.1.3 authentication-results: intel.com; dkim=none (message not signed) header.d=none;intel.com; dmarc=none action=none header.from=intel.com; x-originating-ip: [45.28.143.88] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: cc2c67a3-ab54-4d1c-bd49-08d85069ff09 x-ms-traffictypediagnostic: BYAPR11MB3016: x-ld-processed: 46c98d88-e344-4ed4-8496-4ed7712e255d,ExtAddr x-ms-exchange-transport-forked: True x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:513; x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: X7l3aOoJxzwbZixySXkwSFqwbPEf8Wks9Nx19hIfWKqAwdwf0wd1TqgZ5IaU3ubHw/c/teDVSbUkyB8D5BoQjRuYp42C/ugsMVwQ2msBr/ZdY8bg7Tcbn/M3VhPPPBLJBaTsgJuWlinej+TVE+AGwlnABZbhdNrnkilzVUlBmawOedmaItOk7Ymet6YpixzLKITb3IQVXdnplbc5wgx9YkEDZJ7jmdxRrWANyeUdpe3EasQdqyhnvzNkZwutG8aLWyFPTIgu6BTnJgvlkUIJ+Qwk8yNI7YZJUk17+tAQa7FD2cgGfEXINw7YO6NeccqFKjKEO4KVlSgJSpDSSLcYxw== x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BY5PR11MB4451.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(376002)(39860400002)(346002)(136003)(366004)(396003)(7696005)(9686003)(6506007)(33656002)(8936002)(110136005)(53546011)(30864003)(478600001)(86362001)(55016002)(316002)(54906003)(5660300002)(2906002)(52536014)(66556008)(8676002)(66946007)(71200400001)(26005)(64756008)(66446008)(186003)(76116006)(83380400001)(66476007)(4326008); DIR:OUT; SFP:1102; x-ms-exchange-antispam-messagedata: G6VYMlMgHjcwMb5qiPBzyAnmc88fhENJYozR+ISejuQ5p96zCAfksGMWZoenuLxGbnBPNO29NHRyMxElpAZeahtdWsn8KiRlLu61+IbynOs2f84O3FPZmNtPb2dxW8iAvS3uL0rb4hSbVNSXSi4OAgVzJIuDTWfzWOIsyaPKop1jVutgzcuLNREjTFZcHn3jON/XUq4y5RUuEF9K4afKeedWnaZjjw+BUBiW9ql6APw3PCocIL1C58cp7Ug9VwHuzdMgPhfT61llmM7jhzBUzHaoF0LT/l+5kW4ap1rrb14TD7DvShU+lKmV2hdniniehx3fnTCEltaEfiUV9EarKyiO0gNVx1kBz0pZ21O8PjckMKInQcwogHjfWyWZgHVSP81HP+jFhg7PFjKSkcTqARuXEVQbWiEabf7mDNjGccsLWjg5yJtKlR25oJH8rkMiJYRrn4gxtrKaBV/15UMnyAUqNYSh90p4KTthevyjr/IKbOxr6j0jDRaRHyYmwqP4hJkuevH7cJE0WGC9ZSpoloYMBwHEeNSyfn5HQhY48agspnhHMwAN8M4iP9Z15EJZHwOzmZSLLBXiz9x/BEvYlVWZ8xXoiDQgrNISu0nLnR/GYmqRnefJvj3WzBS/ANJJvFhpOt0CQFbTkHqllDeTkw== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: BY5PR11MB4451.namprd11.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: cc2c67a3-ab54-4d1c-bd49-08d85069ff09 X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Sep 2020 00:32:24.8994 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 46c98d88-e344-4ed4-8496-4ed7712e255d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: cYk/RlZyFwlwNTLdC+gnWL1jAJ731imAHMLV4mhC82u6RkZpENZ4kkxiPt4stT0OD+m4/VTTY74mv95TwDeMzRW1v7TlPM/NMn0dsG6NuYU= X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3016 X-OriginatorOrg: intel.com Subject: Re: [dpdk-dev] [PATCH v3 35/37] doc: remove reference to make in tools guides X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Ciara,=20 Fine with me for test-bbdev. (Ignore my parallel comment to point more expl= icitly to the build stage directory, that is already fine below).=20 Acked-by: Nicolas Chautru > -----Original Message----- > From: Power, Ciara > Sent: Thursday, September 3, 2020 8:27 AM > To: dev@dpdk.org > Cc: Power, Ciara ; Mcnamara, John > ; Kovacevic, Marko > ; Doherty, Declan ; > Pattan, Reshma ; Tahhan, Maryam > ; Chautru, Nicolas ; > Jerin Jacob > Subject: [PATCH v3 35/37] doc: remove reference to make in tools guides >=20 > Make is no longer supported for compiling DPDK, references are now remove= d > in the documentation. >=20 > Signed-off-by: Ciara Power > Reviewed-by: Kevin Laatz > --- > doc/guides/tools/comp_perf.rst | 10 ++------- > doc/guides/tools/cryptoperf.rst | 20 +++-------------- > doc/guides/tools/pdump.rst | 15 ++++++------- > doc/guides/tools/proc_info.rst | 2 +- > doc/guides/tools/testbbdev.rst | 36 +++++++++---------------------- > doc/guides/tools/testeventdev.rst | 21 ++++++++---------- > 6 files changed, 31 insertions(+), 73 deletions(-) >=20 > diff --git a/doc/guides/tools/comp_perf.rst b/doc/guides/tools/comp_perf.= rst > index ee585d1024..1b33dc4e91 100644 > --- a/doc/guides/tools/comp_perf.rst > +++ b/doc/guides/tools/comp_perf.rst > @@ -100,13 +100,7 @@ Application Options Compiling the Tool > ------------------ >=20 > -**Step 1: PMD setting** > - > -The ``dpdk-test-compress-perf`` tool depends on compression device drive= rs > PMD which -can be disabled by default in the build configuration file > ``common_base``. > -The compression device drivers PMD which should be tested can be enabled > by setting e.g.:: > - > - CONFIG_RTE_LIBRTE_PMD_ISAL=3Dy > +See :doc:`../linux_gsg/build_dpdk.rst` for compilation steps. >=20 >=20 > Running the Tool > @@ -116,5 +110,5 @@ The tool has a number of command line options. Here > is the sample command line: >=20 > .. code-block:: console >=20 > - ./build/app/dpdk-test-compress-perf -l 4 -- --driver-name compress_q= at -- > input-file test.txt --seg-sz 8192 > + .//app/dpdk-test-compress-perf -l 4 -- --driver-name > + compress_qat --input-file test.txt --seg-sz 8192 > --compress-level 1:1:9 --num-iter 10 --extended-input-sz 1048576 --= max- > num-sgl-segs 16 --huffman-enc fixed diff --git a/doc/guides/tools/cryptop= erf.rst > b/doc/guides/tools/cryptoperf.rst index 28b729dbda..e7ea2ba1a5 100644 > --- a/doc/guides/tools/cryptoperf.rst > +++ b/doc/guides/tools/cryptoperf.rst > @@ -33,19 +33,8 @@ the hardware accelerator fully loaded and so measure > maximum throughput. > Compiling the Application > ------------------------- >=20 > -**Step 1: PMD setting** >=20 > -The ``dpdk-test-crypto-perf`` tool depends on crypto device drivers PMD = which > -are disabled by default in the build configuration file ``common_base``. > -The crypto device drivers PMD which should be tested can be enabled by > setting:: > - > - CONFIG_RTE_LIBRTE_PMD_=3Dy > - > -Setting example for open ssl PMD:: > - > - CONFIG_RTE_LIBRTE_PMD_OPENSSL=3Dy > - > -**Step 2: Linearization setting** > +**Step 1: Linearization setting** >=20 > It is possible linearized input segmented packets just before crypto ope= ration > for devices which doesn't support scatter-gather, and allows to measure @= @ - > 56,13 +45,10 @@ To set on the linearization options add below definition = to the >=20 > #define CPERF_LINEARIZATION_ENABLE >=20 > -**Step 3: Build the application** > +**Step 2: Build the application** >=20 > -Execute the ``dpdk-setup.sh`` script to build the DPDK library together = with the > -``dpdk-test-crypto-perf`` application. > +See :doc:`../linux_gsg/build_dpdk.rst` for compilation steps. >=20 > -Initially, the user must select a DPDK target to choose the correct targ= et type - > and compiler options to use when building the libraries. > The user must have all libraries, modules, updates and compilers install= ed in > the system prior to this, as described in the earlier chapters in this G= etting > Started Guide. > diff --git a/doc/guides/tools/pdump.rst b/doc/guides/tools/pdump.rst inde= x > 8a499c6c5b..70f03db9cc 100644 > --- a/doc/guides/tools/pdump.rst > +++ b/doc/guides/tools/pdump.rst > @@ -19,12 +19,9 @@ a DPDK secondary process and is capable of enabling > packet capture on dpdk ports > framework initialization code. Refer ``app/test-pmd/testpmd.c`` > code to see how this is done. >=20 > - * The ``dpdk-pdump`` tool depends on libpcap based PMD which is > disabled > - by default in the build configuration files, > - owing to an external dependency on the libpcap development files > - which must be installed on the board. > - Once the libpcap development files are installed, the libpcap ba= sed PMD > - can be enabled by setting CONFIG_RTE_LIBRTE_PMD_PCAP=3Dy and > recompiling the DPDK. > + * The ``dpdk-pdump`` tool depends on libpcap based PMD which must = be > + installed on the board. > + Once the libpcap development files are installed, recompile the = DPDK. >=20 > * The ``dpdk-pdump`` tool runs as a DPDK secondary process. It exi= ts when > the primary application exits. > @@ -37,7 +34,7 @@ The tool has a number of command line options: >=20 > .. code-block:: console >=20 > - ./build/app/dpdk-pdump -- > + .//app/dpdk-pdump -- > [--multi] > --pdump '(port=3D | device_id=3D), > (queue=3D), @@ -120,5 +117,= 5 @@ Example >=20 > .. code-block:: console >=20 > - $ sudo ./build/app/dpdk-pdump -l 3 -- --pdump 'port=3D0,queue=3D*,rx- > dev=3D/tmp/rx.pcap' > - $ sudo ./build/app/dpdk-pdump -l 3,4,5 -- --multi --pdump > 'port=3D0,queue=3D*,rx-dev=3D/tmp/rx-1.pcap' --pdump 'port=3D1,queue=3D*,= rx- > dev=3D/tmp/rx-2.pcap' > + $ sudo .//app/dpdk-pdump -l 3 -- --pdump 'port=3D0,queue= =3D*,rx- > dev=3D/tmp/rx.pcap' > + $ sudo .//app/dpdk-pdump -l 3,4,5 -- --multi --pdump > 'port=3D0,queue=3D*,rx-dev=3D/tmp/rx-1.pcap' --pdump 'port=3D1,queue=3D*,= rx- > dev=3D/tmp/rx-2.pcap' > diff --git a/doc/guides/tools/proc_info.rst b/doc/guides/tools/proc_info.= rst > index 0390b9c589..9772d97ef0 100644 > --- a/doc/guides/tools/proc_info.rst > +++ b/doc/guides/tools/proc_info.rst > @@ -17,7 +17,7 @@ The application has a number of command line options: >=20 > .. code-block:: console >=20 > - ./$(RTE_TARGET)/app/dpdk-procinfo -- -m | [-p PORTMASK] [--stats | --= xstats > | > + .//app/dpdk-procinfo -- -m | [-p PORTMASK] [--stats | > + --xstats | > --stats-reset | --xstats-reset] [ --show-port | --show-tm | --show-cr= ypto | > --show-ring[=3Dname] | --show-mempool[=3Dname] | --iter-mempool=3Dnam= e ] >=20 > diff --git a/doc/guides/tools/testbbdev.rst b/doc/guides/tools/testbbdev.= rst > index 393c3e9d0d..1fea7e0aa4 100644 > --- a/doc/guides/tools/testbbdev.rst > +++ b/doc/guides/tools/testbbdev.rst > @@ -13,25 +13,10 @@ parameters passed to a python running script. > Compiling the Application > ------------------------- >=20 > -**Step 1: PMD setting** > +**Build the application** >=20 > -The ``dpdk-test-bbdev`` tool depends on crypto device drivers PMD which = -are > disabled by default in the build configuration file ``common_base``. > -The bbdevice drivers PMD which should be tested can be enabled by settin= g > +See :doc:`../linux_gsg/build_dpdk.rst` for compilation steps. >=20 > - ``CONFIG_RTE_LIBRTE_PMD_=3Dy`` > - > -Setting example for (*baseband_turbo_sw*) PMD > - > - ``CONFIG_RTE_LIBRTE_PMD_BBDEV_TURBO_SW=3Dy`` > - > -**Step 2: Build the application** > - > -Execute the ``dpdk-setup.sh`` script to build the DPDK library together = with the > -``dpdk-test-bbdev`` application. > - > -Initially, the user must select a DPDK target to choose the correct targ= et type - > and compiler options to use when building the libraries. > The user must have all libraries, modules, updates and compilers install= ed in > the system prior to this, as described in the earlier chapters in this G= etting > Started Guide. > @@ -60,7 +45,7 @@ The following are the command-line options: >=20 > ``-p TESTAPP_PATH, --testapp_path TESTAPP_PATH`` > Indicates the path to the bbdev test app. If not specified path is set = based > - on *$RTE_SDK* environment variable concatenated with > "*/build/app/testbbdev*". > + on "../.." concatenated with "*/build/app/testbbdev*". >=20 > ``-e EAL_PARAMS, --eal_params EAL_PARAMS`` > Specifies EAL arguments which are passed to the test app. For more deta= ils, > @@ -82,9 +67,8 @@ The following are the command-line options: >=20 > ``-v TEST_VECTOR [TEST_VECTOR ...], --test_vector TEST_VECTOR > [TEST_VECTOR ...]`` > Specifies paths to the test vector files. If not specified path is set = based > - on *$RTE_SDK* environment variable concatenated with > - "*/app/test-bbdev/test_vectors/bbdev_null.data*" and indicates default > - data file. > + on "../.." concatenated with "*/app/test- > bbdev/test_vectors/bbdev_null.data*" > +and indicates default data file. >=20 > **Example usage:** >=20 > @@ -259,8 +243,8 @@ They are chosen to have a good coverage across sizes > and processing parameters while still keeping their number limited as pa= rt of > sanity regression. >=20 > -Shortened tree of isg_cid-wireless_dpdk_ae with dpdk compiled for -x86_6= 4- > native-linux-icc target: > +Shortened tree of isg_cid-wireless_dpdk_ae with dpdk compiled and > +output to the build directory: >=20 > :: >=20 > @@ -268,7 +252,7 @@ x86_64-native-linux-icc target: > |-- test-bbdev > |-- test_vectors >=20 > - |-- x86_64-native-linux-icc > + |-- build > |-- app > |-- testbbdev >=20 > @@ -277,7 +261,7 @@ All bbdev devices >=20 > .. code-block:: console >=20 > - ./test-bbdev.py -p ../../x86_64-native-linux-icc/app/testbbdev > + ./test-bbdev.py -p ../../build/app/dpdk-test-bbdev > -v turbo_dec_default.data >=20 > It runs all available tests using the test vector filled based on @@ -29= 1,7 > +275,7 @@ baseband turbo_sw device >=20 > .. code-block:: console >=20 > - ./test-bbdev.py -p ../../x86_64-native-linux-icc/app/testbbdev > + ./test-bbdev.py -p ../../build/app/dpdk-test-bbdev > -e=3D"--vdev=3Dbaseband_turbo_sw" -t 120 -c validation > -v ./test_vectors/* -n 64 -b 8 32 >=20 > diff --git a/doc/guides/tools/testeventdev.rst > b/doc/guides/tools/testeventdev.rst > index 2ed67a6340..00387ec4ed 100644 > --- a/doc/guides/tools/testeventdev.rst > +++ b/doc/guides/tools/testeventdev.rst > @@ -15,11 +15,8 @@ Compiling the Application >=20 > **Build the application** >=20 > -Execute the ``dpdk-setup.sh`` script to build the DPDK library together = with the > -``dpdk-test-eventdev`` application. > +See :doc:`../linux_gsg/build_dpdk.rst` for compilation steps. >=20 > -Initially, the user must select a DPDK target to choose the correct targ= et type - > and compiler options to use when building the libraries. > The user must have all libraries, modules, updates and compilers install= ed in > the system prior to this, as described in the earlier chapters in this G= etting > Started Guide. > @@ -251,7 +248,7 @@ Example command to run order queue test: >=20 > .. code-block:: console >=20 > - sudo build/app/dpdk-test-eventdev --vdev=3Devent_sw0 -- \ > + sudo /app/dpdk-test-eventdev --vdev=3Devent_sw0 -- \ > --test=3Dorder_queue --plcores 1 --wlcores 2,3 >=20 >=20 > @@ -314,7 +311,7 @@ Example command to run order ``all types queue`` test= : >=20 > .. code-block:: console >=20 > - sudo build/app/dpdk-test-eventdev --vdev=3Devent_octeontx -- \ > + sudo /app/dpdk-test-eventdev --vdev=3Devent_octeontx -- \ > --test=3Dorder_atq --plcores 1 --wlcores 2,3 >=20 >=20 > @@ -414,7 +411,7 @@ Example command to run perf queue test: >=20 > .. code-block:: console >=20 > - sudo build/app/dpdk-test-eventdev -c 0xf -s 0x1 --vdev=3Devent_sw0 --= \ > + sudo /app/dpdk-test-eventdev -c 0xf -s 0x1 > + --vdev=3Devent_sw0 -- \ > --test=3Dperf_queue --plcores=3D2 --wlcore=3D3 --stlist=3Dp --nb= _pkts=3D0 >=20 > Example command to run perf queue test with ethernet ports: > @@ -428,7 +425,7 @@ Example command to run perf queue test with event > timer adapter: >=20 > .. code-block:: console >=20 > - sudo build/app/dpdk-test-eventdev --vdev=3D"event_octeontx" -- \ > + sudo /app/dpdk-test-eventdev --vdev=3D"event_octeontx" -- > + \ > --wlcores 4 --plcores 12 --test perf_queue --stlist=3Da = \ > --prod_type_timerdev --fwd_latency >=20 > @@ -514,14 +511,14 @@ Example command to run perf ``all types queue`` > test: >=20 > .. code-block:: console >=20 > - sudo build/app/dpdk-test-eventdev --vdev=3Devent_octeontx -- \ > + sudo /app/dpdk-test-eventdev --vdev=3Devent_octeontx -- \ > --test=3Dperf_atq --plcores=3D2 --wlcore=3D3 --stlist=3D= p --nb_pkts=3D0 >=20 > Example command to run perf ``all types queue`` test with event timer > adapter: >=20 > .. code-block:: console >=20 > - sudo build/app/dpdk-test-eventdev --vdev=3D"event_octeontx" -- \ > + sudo /app/dpdk-test-eventdev --vdev=3D"event_octeontx" -- > + \ > --wlcores 4 --plcores 12 --test perf_atq --verbose 20 \ > --stlist=3Da --prod_type_timerdev --fwd_latency >=20 > @@ -633,7 +630,7 @@ Example command to run pipeline queue test: >=20 > .. code-block:: console >=20 > - sudo build/app/dpdk-test-eventdev -c 0xf -s 0x8 --vdev=3Devent_sw0 -= - \ > + sudo /app/dpdk-test-eventdev -c 0xf -s 0x8 > + --vdev=3Devent_sw0 -- \ > --test=3Dpipeline_queue --wlcore=3D1 --prod_type_ethdev --stlist= =3Da >=20 >=20 > @@ -725,5 +722,5 @@ Example command to run pipeline queue test: >=20 > .. code-block:: console >=20 > - sudo build/app/dpdk-test-eventdev -c 0xf -s 0x8 --vdev=3Devent_sw0 -= - \ > + sudo /app/dpdk-test-eventdev -c 0xf -s 0x8 > + --vdev=3Devent_sw0 -- \ > --test=3Dpipeline_atq --wlcore=3D1 --prod_type_ethdev --stlist= =3Da > -- > 2.17.1