From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH] docs: fix wrong setting up for spp_vf
Date: Thu, 4 Apr 2019 19:09:16 +0900 [thread overview]
Message-ID: <1554372556-18415-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Fix wrong descriptions of spp_vf setup in usecases section.
Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
docs/guides/usecases/spp_vf.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/guides/usecases/spp_vf.rst b/docs/guides/usecases/spp_vf.rst
index d2092e2..b7c304b 100644
--- a/docs/guides/usecases/spp_vf.rst
+++ b/docs/guides/usecases/spp_vf.rst
@@ -132,7 +132,7 @@ Ensure NICs, ``ens0`` and ``ens1`` in this case, are upped on remote host
# terminal 1 on remote host
# Configure ip address of ens0
- $ sudo ifconfig ens0 192.168.140.1 255.255.255.0 up
+ $ sudo ifconfig ens0 192.168.140.1 netmask 255.255.255.0 up
Add arp entries of MAC addresses statically to be resolved.
@@ -233,7 +233,7 @@ Finally, terminate ``spp_vf`` by using ``exit`` or ``bye sec``.
.. code-block:: console
- spp > vf 0; exit
+ spp > vf 1; exit
.. _spp_usecases_vf_ssh:
@@ -443,11 +443,11 @@ After VMs are launched, login to ``spp-vm1`` first to configure.
.. note::
To avoid asked for unknown keys while login VMs, use
- ``-oStrictHostKeyChecking=no`` option for ssh.
+ ``-o StrictHostKeyChecking=no`` option for ssh.
.. code-block:: console
- $ ssh -oStrictHostKeyChecking=no sppuser at 192.168.122.31
+ $ ssh -o StrictHostKeyChecking=no sppuser at 192.168.122.31
Up interfaces and disable TCP offload to avoid ssh login is failed.
--
2.7.4
reply other threads:[~2019-04-04 10:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1554372556-18415-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=spp@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).