From: x-fn-spp@sl.ntt-tx.co.jp
To: ferruh.yigit@intel.com, yasufum.o@gmail.com
Cc: spp@dpdk.org
Subject: [spp] [PATCH 1/7] rcps: add vhost related rcps for spp_nfv
Date: Thu, 9 Jan 2020 11:51:07 +0900 [thread overview]
Message-ID: <202001090251.0092pDG6027694@imss04.silk.ntt-tx.co.jp> (raw)
In-Reply-To: <20200109025113.22689-1-x-fn-spp@sl.ntt-tx.co.jp>
From: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
This patch set adds vhost related rcps for spp_nfv.
Signed-off-by: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
---
.../single_with_vhost/1_vhost_single_unidir.rcps | 10 ++++++++++
.../usecases/spp_nfv/single_with_vhost/2_clean.rcps | 9 +++++++++
2 files changed, 19 insertions(+)
create mode 100644 recipes/usecases/spp_nfv/single_with_vhost/1_vhost_single_unidir.rcps
create mode 100644 recipes/usecases/spp_nfv/single_with_vhost/2_clean.rcps
diff --git a/recipes/usecases/spp_nfv/single_with_vhost/1_vhost_single_unidir.rcps b/recipes/usecases/spp_nfv/single_with_vhost/1_vhost_single_unidir.rcps
new file mode 100644
index 0000000..86841f2
--- /dev/null
+++ b/recipes/usecases/spp_nfv/single_with_vhost/1_vhost_single_unidir.rcps
@@ -0,0 +1,10 @@
+# Add vhost PMDs
+nfv 1; add vhost:0
+nfv 1; add vhost:1
+
+# Patch ports
+nfv 1; patch phy:0 vhost:0
+nfv 1; patch vhost:1 phy:1
+
+# Start forwarding
+nfv 1; forward
diff --git a/recipes/usecases/spp_nfv/single_with_vhost/2_clean.rcps b/recipes/usecases/spp_nfv/single_with_vhost/2_clean.rcps
new file mode 100644
index 0000000..aa05798
--- /dev/null
+++ b/recipes/usecases/spp_nfv/single_with_vhost/2_clean.rcps
@@ -0,0 +1,9 @@
+# Stop forwarding
+nfv 1; stop
+
+# Clear all of patches
+nfv 1; patch reset
+
+# Delete vhost PMDs
+nfv 1; del vhost:0
+nfv 1; del vhost:1
--
2.17.1
next parent reply other threads:[~2020-01-09 2:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200109025113.22689-1-x-fn-spp@sl.ntt-tx.co.jp>
2020-01-09 2:51 ` x-fn-spp [this message]
2020-01-09 2:51 ` [spp] [PATCH 2/7] rcps: fix rcps for setting up spp_vf x-fn-spp
2020-01-09 2:51 ` [spp] [PATCH 3/7] rcps: fix typos " x-fn-spp
2020-01-09 2:51 ` [spp] [PATCH 4/7] rcps: fix rcps for shutting down spp_vf x-fn-spp
2020-01-09 2:51 ` [spp] [PATCH 5/7] rcps: add rcps for spp_mirror x-fn-spp
2020-01-09 2:51 ` [spp] [PATCH 6/7] docs: adds spp-vm1.xml x-fn-spp
2020-01-09 2:51 ` [spp] [PATCH 7/7] docs: fix incorrect commands in usecases x-fn-spp
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=202001090251.0092pDG6027694@imss04.silk.ntt-tx.co.jp \
--to=x-fn-spp@sl.ntt-tx.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=spp@dpdk.org \
--cc=yasufum.o@gmail.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).