Soft Patch Panel
 help / color / mirror / Atom feed
From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com
Cc: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Subject: [spp] [PATCH 03/11] docs: resize figures of SPP
Date: Fri, 31 Aug 2018 18:14:33 +0900	[thread overview]
Message-ID: <20180831091441.39055-4-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <20180831091441.39055-1-ogawa.yasufumi@lab.ntt.co.jp>

From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>

This patch is for resizing figures in SPP docs for PDF format.

Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
 docs/guides/commands/experimental.rst |  6 +++---
 docs/guides/overview.rst              |  7 ++++---
 docs/guides/setup/use_cases.rst       | 24 ++++++++----------------
 3 files changed, 15 insertions(+), 22 deletions(-)

diff --git a/docs/guides/commands/experimental.rst b/docs/guides/commands/experimental.rst
index 42ba371..81dceac 100644
--- a/docs/guides/commands/experimental.rst
+++ b/docs/guides/commands/experimental.rst
@@ -94,7 +94,7 @@ and save this script as
 .. _figure_topo_term_exp:
 
 .. figure:: ../images/commands/expr/topo_term_exp.*
-   :width: 440 em
+   :width: 67%
 
    topo term example
 
@@ -202,7 +202,7 @@ following.
 .. _figure_topo_subg_before:
 
 .. figure:: ../images/commands/expr/topo_subg_before.*
-   :width: 440 em
+   :width: 67%
 
    Before using topo_subgraph
 
@@ -223,7 +223,7 @@ In this case, add subgraph ``guest_vm`` and includes resoures
 .. _figure_topo_subg_after:
 
 .. figure:: ../images/commands/expr/topo_subg_after.*
-   :width: 440 em
+   :width: 67%
 
    After using topo_subgraph
 
diff --git a/docs/guides/overview.rst b/docs/guides/overview.rst
index fd1415f..9e1c426 100644
--- a/docs/guides/overview.rst
+++ b/docs/guides/overview.rst
@@ -40,9 +40,10 @@ Overview
 functionality for Service Function Chaining in
 NFV (Network Function Virtualization).
 
-.. image:: images/overview/spp_overview.svg
-   :height: 350 em
-   :width: 350 em
+.. figure:: images/overview/spp_overview.*
+    :width: 50%
+
+    SPP overview
 
 With SPP, user is able to configure network easily and dynamically
 via simple patch panel like interface.
diff --git a/docs/guides/setup/use_cases.rst b/docs/guides/setup/use_cases.rst
index 2c83fe0..1e31949 100644
--- a/docs/guides/setup/use_cases.rst
+++ b/docs/guides/setup/use_cases.rst
@@ -86,8 +86,7 @@ Confirm that status of ``sec 1`` is updated.
 .. _figure_spp_nfv_as_l2fwd:
 
 .. figure:: ../images/setup/use_cases/spp_nfv_l2fwd.*
-   :height: 380 em
-   :width: 380 em
+   :width: 52%
 
    spp_nfv as l2fwd
 
@@ -149,8 +148,7 @@ from ``phy:1`` to ``phy:0`` for ``sec 2``.
 .. _figure_spp_two_nfv_as_l2fwd:
 
 .. figure:: ../images/setup/use_cases/spp_two_nfv_l2fwd.*
-   :height: 420 em
-   :width: 420 em
+   :width: 52%
 
    Two spp_nfv as l2fwd
 
@@ -171,8 +169,7 @@ Patch ``phy:0`` to ``phy:0`` for ``sec 1`` and
 .. _figure_spp_two_nfv_loopback:
 
 .. figure:: ../images/setup/use_cases/spp_two_nfv_loopback.*
-   :height: 420 em
-   :width: 420 em
+   :width: 52%
 
    Two spp_nfv for loopback
 
@@ -240,8 +237,7 @@ Then, connect it with ``patch`` subcommand.
 .. _figure_spp_uni_directional_l2fwd:
 
 .. figure:: ../images/setup/use_cases/spp_unidir_l2fwd.*
-   :height: 460 em
-   :width: 460 em
+   :width: 52%
 
    Uni-Directional l2fwd
 
@@ -295,8 +291,7 @@ Then, add ``ring 0`` and ``ring 1`` to ``sec 2``.
 .. _figure_spp_bi_directional_l2fwd:
 
 .. figure:: ../images/setup/use_cases/spp_bidir_l2fwd.*
-   :height: 460 em
-   :width: 460 em
+   :width: 52%
 
    Bi-Directional l2fwd
 
@@ -361,8 +356,7 @@ with ``sec 2``.
 .. _figure_spp_uni_directional_l2fwd_vhost:
 
 .. figure:: ../images/setup/use_cases/spp_unidir_l2fwd_vhost.*
-   :height: 460 em
-   :width: 460 em
+   :width: 52%
 
    Uni-Directional l2fwd with vhost
 
@@ -419,8 +413,7 @@ As the first usecase, add a pcap PMD and capture incoming packets from
 .. _figure_spp_pcap_incoming:
 
 .. figure:: ../images/setup/use_cases/spp_pcap_incoming.*
-   :height: 380 em
-   :width: 380 em
+   :width: 50%
 
    Rapture incoming packets
 
@@ -461,8 +454,7 @@ Then, add pcap PMD to another ``spp_nfv`` with index ``2``.
 .. _figure_spp_pcap_restoring:
 
 .. figure:: ../images/setup/use_cases/spp_pcap_restoring.*
-   :height: 380 em
-   :width: 380 em
+   :width: 52%
 
    Restore dumped packets
 
-- 
2.7.4

  parent reply	other threads:[~2018-08-31  9:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31  9:14 [spp] [PATCH 00/11] PDF documentation support ogawa.yasufumi
2018-08-31  9:14 ` [spp] [PATCH 01/11] docs: move SPP VF images ogawa.yasufumi
2018-08-31  9:14 ` [spp] [PATCH 02/11] docs: resize figures of SPP VF ogawa.yasufumi
2018-08-31  9:14 ` ogawa.yasufumi [this message]
2018-08-31  9:14 ` [spp] [PATCH 04/11] docs: resize figures of SPP container ogawa.yasufumi
2018-08-31  9:14 ` [spp] [PATCH 05/11] docs: add script for generating PDF images ogawa.yasufumi
2018-08-31  9:14 ` [spp] [PATCH 06/11] project: update gitignore to exclude PDF files ogawa.yasufumi
2018-08-31  9:14 ` [spp] [PATCH 07/11] docs: add sphinx config to PDF ogawa.yasufumi
2018-08-31  9:14 ` [spp] [PATCH 08/11] makefile: add make option to compile PDF doc ogawa.yasufumi
2018-08-31  9:14 ` [spp] [PATCH 09/11] makefile: fix bug of PDF compilation ogawa.yasufumi
2018-08-31  9:14 ` [spp] [PATCH 10/11] docs: refactor for character length ogawa.yasufumi
2018-08-31  9:14 ` [spp] [PATCH 11/11] docs: fix typo of label 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=20180831091441.39055-4-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).