DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
	dev@dpdk.org, techboard@dpdk.org,
	Stephen Hemminger <stephen@networkplumber.org>,
	Bruce Richardson <bruce.richardson@intel.com>,
	conor.walsh@intel.com
Subject: [dpdk-dev] [PATCH v2 3/6] usertools/setup: remove running built applications
Date: Thu, 26 Nov 2020 14:18:29 +0000	[thread overview]
Message-ID: <20201126141832.2277628-4-ferruh.yigit@intel.com> (raw)
In-Reply-To: <20201126141832.2277628-1-ferruh.yigit@intel.com>

Running application relies on make based build variable 'RTE_TARGET' to
find the location of the applications, which is not valid anymore.

Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
 doc/guides/linux_gsg/quick_start.rst | 42 +++++++---------------
 usertools/dpdk-setup.sh              | 52 ++--------------------------
 2 files changed, 14 insertions(+), 80 deletions(-)

diff --git a/doc/guides/linux_gsg/quick_start.rst b/doc/guides/linux_gsg/quick_start.rst
index 14c4c7763aed..f46c50d04b65 100644
--- a/doc/guides/linux_gsg/quick_start.rst
+++ b/doc/guides/linux_gsg/quick_start.rst
@@ -20,8 +20,6 @@ The dpdk-setup.sh script, found in the usertools subdirectory, allows the user t
 
 *   Set up permissions for using VFIO as a non-privileged user
 
-*   Run the test and testpmd applications
-
 *   Look at hugepages in the meminfo
 
 *   List hugepages in ``/mnt/huge``
@@ -41,17 +39,11 @@ The user configures the Linux* environment to support the running of DPDK applic
 Hugepages can be set up for NUMA or non-NUMA systems. Any existing hugepages will be removed.
 Network ports may be bound to DPDK kernel module for DPDK application use.
 
-**Step 2: Run an Application**
-
-The user may run the test application once the other steps have been performed.
-The test application allows the user to run a series of functional tests for the DPDK.
-The testpmd application, which supports the receiving and sending of packets, can also be run.
-
-**Step 3: Examining the System**
+**Step 2: Examining the System**
 
 This step provides some tools for examining the status of hugepage mappings.
 
-**Step 4: System Cleanup**
+**Step 3: System Cleanup**
 
 The final step has options for restoring the system to its original state.
 
@@ -96,39 +88,29 @@ Some options in the script prompt the user for further data before proceeding.
 
     ------------------------------------------------------------------------
 
-    Step 2: Run test application for linux environment
-
-    ------------------------------------------------------------------------
-
-    [8] Run test application ($RTE_TARGET/app/test)
-
-    [9] Run testpmd application in interactive mode ($RTE_TARGET/app/testpmd)
-
-    ------------------------------------------------------------------------
-
-    Step 3: Other tools
+    Step 2: Other tools
 
     ------------------------------------------------------------------------
 
-    [10] List hugepage info from /proc/meminfo
+    [8] List hugepage info from /proc/meminfo
 
     ------------------------------------------------------------------------
 
-    Step 4: Uninstall and system cleanup
+    Step 3: Uninstall and system cleanup
 
     ------------------------------------------------------------------------
 
-    [11] Unbind NICs from IGB UIO driver
+    [9] Unbind NICs from IGB UIO driver
 
-    [12] Remove IGB UIO module
+    [10] Remove IGB UIO module
 
-    [13] Remove VFIO module
+    [11] Remove VFIO module
 
-    [14] Remove KNI module
+    [12] Remove KNI module
 
-    [15] Remove hugepage mappings
+    [13] Remove hugepage mappings
 
-    [16] Exit Script
+    [14] Exit Script
 
     Option:
 
@@ -136,7 +118,7 @@ The following selection demonstrates the starting of the DPDK UIO driver.
 
 .. code-block:: console
 
-    Option: 12
+    Option: 10
 
     Unloading any existing DPDK UIO module
     Loading DPDK UIO module
diff --git a/usertools/dpdk-setup.sh b/usertools/dpdk-setup.sh
index bcf0c843678f..759f6c096536 100755
--- a/usertools/dpdk-setup.sh
+++ b/usertools/dpdk-setup.sh
@@ -17,11 +17,6 @@ echo "--------------------------------------------------------------------------
 
 HUGEPGSZ=`cat /proc/meminfo  | grep Hugepagesize | cut -d : -f 2 | tr -d ' '`
 
-#
-# Application EAL parameters for setting memory options (amount/channels/ranks).
-#
-EAL_PARAMS='-n 4'
-
 #
 # Sets QUIT variable so script will finish.
 #
@@ -252,34 +247,6 @@ set_numa_pages()
 	create_mnt_huge
 }
 
-#
-# Run unit test application.
-#
-run_test_app()
-{
-	echo ""
-	echo "  Enter hex bitmask of cores to execute test app on"
-	echo "  Example: to execute app on cores 0 to 7, enter 0xff"
-	echo -n "bitmask: "
-	read Bitmask
-	echo "Launching app"
-	sudo ${RTE_TARGET}/app/test -c $Bitmask $EAL_PARAMS
-}
-
-#
-# Run unit testpmd application.
-#
-run_testpmd_app()
-{
-	echo ""
-	echo "  Enter hex bitmask of cores to execute testpmd app on"
-	echo "  Example: to execute app on cores 0 to 7, enter 0xff"
-	echo -n "bitmask: "
-	read Bitmask
-	echo "Launching app"
-	sudo ${RTE_TARGET}/app/testpmd -c $Bitmask $EAL_PARAMS -- -i
-}
-
 #
 # Print hugepage information.
 #
@@ -381,24 +348,10 @@ step1_func()
 	FUNC[7]="set_vfio_permissions"
 }
 
-#
-# Options for running applications.
-#
-step2_func()
-{
-	TITLE="Run test application for linux environment"
-
-	TEXT[1]="Run test application (\$RTE_TARGET/app/test)"
-	FUNC[1]="run_test_app"
-
-	TEXT[2]="Run testpmd application in interactive mode (\$RTE_TARGET/app/testpmd)"
-	FUNC[2]="run_testpmd_app"
-}
-
 #
 # Other options
 #
-step3_func()
+step2_func()
 {
 	TITLE="Other tools"
 
@@ -410,7 +363,7 @@ step3_func()
 #
 # Options for cleaning up the system
 #
-step4_func()
+step3_func()
 {
 	TITLE="Uninstall and system cleanup"
 
@@ -433,7 +386,6 @@ step4_func()
 STEPS[1]="step1_func"
 STEPS[2]="step2_func"
 STEPS[3]="step3_func"
-STEPS[4]="step4_func"
 
 QUIT=0
 
-- 
2.26.2


  parent reply	other threads:[~2020-11-26 14:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 14:18 [dpdk-dev] [PATCH v2 0/6] update dpdk-setup.sh Ferruh Yigit
2020-11-26 14:18 ` [dpdk-dev] [PATCH v2 1/6] usertools/setup: remove make based build Ferruh Yigit
2020-11-26 14:44   ` Walsh, Conor
2020-11-26 14:18 ` [dpdk-dev] [PATCH v2 2/6] usertools/setup: remove inserting custom kernel modules Ferruh Yigit
2020-11-26 14:49   ` Walsh, Conor
2020-11-26 14:18 ` Ferruh Yigit [this message]
2020-11-26 14:55   ` [dpdk-dev] [PATCH v2 3/6] usertools/setup: remove running built applications Walsh, Conor
2020-11-26 14:18 ` [dpdk-dev] [PATCH v2 4/6] usertools/setup: remove hugepage functions Ferruh Yigit
2020-11-26 15:01   ` Walsh, Conor
2020-11-26 14:18 ` [dpdk-dev] [PATCH v2 5/6] usertools/setup: fix loading vfio module Ferruh Yigit
2020-11-26 15:05   ` Walsh, Conor
2020-11-26 18:31   ` David Marchand
2020-11-27  9:55     ` Ferruh Yigit
2020-11-27 13:56       ` Thomas Monjalon
2020-11-27 15:29         ` Ferruh Yigit
2020-11-26 14:18 ` [dpdk-dev] [PATCH v2 6/6] usertools/setup: move removal target to 21.11 Ferruh Yigit
2020-11-26 15:13   ` Walsh, Conor
2020-11-26 16:30 ` [dpdk-dev] [PATCH v2 0/6] update dpdk-setup.sh David Marchand

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=20201126141832.2277628-4-ferruh.yigit@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=conor.walsh@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=techboard@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).