From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com, spp@dpdk.org, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 3/5] docs: update how to use section
Date: Mon, 19 Nov 2018 17:00:02 +0900 [thread overview]
Message-ID: <1542614404-18171-4-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <1542614404-18171-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp>
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Update the exmaple of adding vhost because it is changed from `vhost 0`
to specify resource UID as `vhost:0`.
Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
docs/guides/setup/howto_use.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/guides/setup/howto_use.rst b/docs/guides/setup/howto_use.rst
index d52a38a..9c7d81d 100644
--- a/docs/guides/setup/howto_use.rst
+++ b/docs/guides/setup/howto_use.rst
@@ -239,11 +239,11 @@ create ``vhost-user`` and ``virtio-net-pci`` devices on the VM.
Before launching VM, you need to prepare a socket file for creating
``vhost-user`` device.
-Socket file is created from SPP secondary as following.
+Run ``add`` command with resource UID ``vhost:0`` to create socket file.
.. code-block:: console
- spp > sec 1;add vhost 0
+ spp > sec 1;add vhost:0
In this example, create socket file with index 0 from secondary of ID 1.
Socket file is created as ``/tmp/sock0``.
--
2.13.1
next prev parent reply other threads:[~2018-11-19 8:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 7:59 [spp] [PATCH 0/5] Update docs to the latest desigin ogawa.yasufumi
2018-11-19 8:00 ` [spp] [PATCH 1/5] docs: update overview section ogawa.yasufumi
2018-11-19 8:00 ` [spp] [PATCH 2/5] docs: update getting started section ogawa.yasufumi
2018-11-19 8:00 ` ogawa.yasufumi [this message]
2018-11-19 8:00 ` [spp] [PATCH 4/5] docs: update usecases section ogawa.yasufumi
2018-11-19 8:00 ` [spp] [PATCH 5/5] docs: add how to compile for docs ogawa.yasufumi
2018-11-20 9:53 ` [spp] [PATCH v2 0/5] Update docs to the latest desigin ogawa.yasufumi
2018-11-20 9:53 ` [spp] [PATCH v2 1/5] docs: update overview section ogawa.yasufumi
2018-11-20 9:53 ` [spp] [PATCH v2 2/5] docs: update getting started section ogawa.yasufumi
2018-11-20 9:53 ` [spp] [PATCH v2 3/5] docs: update how to use section ogawa.yasufumi
2018-11-20 9:53 ` [spp] [PATCH v2 4/5] docs: update usecases section ogawa.yasufumi
2018-11-20 9:53 ` [spp] [PATCH v2 5/5] docs: add how to compile for docs ogawa.yasufumi
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=1542614404-18171-4-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).