Soft Patch Panel
 help / color / mirror / Atom feed
From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com, spp@dpdk.org, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 5/8] docs: adjust size of images
Date: Thu, 10 Jan 2019 11:10:13 +0900	[thread overview]
Message-ID: <1547086216-27422-6-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <1547086216-27422-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp>

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

Font size in some of images is too small because of inappropriate
ratio. This update is to adjust the size of image ratio.

Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
 docs/guides/design/spp_secondary.rst       |  2 +-
 docs/guides/setup/howto_use.rst            |  2 +-
 docs/guides/tools/sppc/getting_started.rst |  2 +-
 docs/guides/tools/sppc/overview.rst        |  2 +-
 docs/guides/tools/sppc/usecases.rst        |  6 +++---
 docs/guides/use_cases/spp_nfv.rst          | 16 ++++++++--------
 6 files changed, 15 insertions(+), 15 deletions(-)

diff --git a/docs/guides/design/spp_secondary.rst b/docs/guides/design/spp_secondary.rst
index 9d11f74..a784e10 100644
--- a/docs/guides/design/spp_secondary.rst
+++ b/docs/guides/design/spp_secondary.rst
@@ -66,7 +66,7 @@ entry has the destination port ID.
 .. _figure_design_spp_sec_nfv_port_fwd_array:
 
 .. figure:: ../images/design/spp_design_spp_sec_nfv.*
-   :width: 75%
+   :width: 80%
 
    Forwarding by referring ports_fwd_array
 
diff --git a/docs/guides/setup/howto_use.rst b/docs/guides/setup/howto_use.rst
index cbc20af..51ad8da 100644
--- a/docs/guides/setup/howto_use.rst
+++ b/docs/guides/setup/howto_use.rst
@@ -129,7 +129,7 @@ soure or destination of phy ports.
 .. _figure_spp_howto_multi_spp:
 
 .. figure:: ../images/setup/howto_use/spp_howto_multi_spp.*
-   :width: 70%
+   :width: 80%
 
    Multiple SPP nodes
 
diff --git a/docs/guides/tools/sppc/getting_started.rst b/docs/guides/tools/sppc/getting_started.rst
index 0ae0978..c0970a3 100644
--- a/docs/guides/tools/sppc/getting_started.rst
+++ b/docs/guides/tools/sppc/getting_started.rst
@@ -277,7 +277,7 @@ and start forwarding from testpmd.
 .. _figure_sppc_gsg_testpmd:
 
 .. figure:: ../../images/tools/sppc/sppc_gsg_testpmd.*
-   :width: 50%
+   :width: 58%
 
    SPP and testpmd on containers
 
diff --git a/docs/guides/tools/sppc/overview.rst b/docs/guides/tools/sppc/overview.rst
index e4b3b62..043bc8d 100644
--- a/docs/guides/tools/sppc/overview.rst
+++ b/docs/guides/tools/sppc/overview.rst
@@ -22,6 +22,6 @@ an app container.
 .. _figure_sppc_overview:
 
 .. figure:: ../../images/tools/sppc/sppc_overview.*
-   :width: 85%
+   :width: 95%
 
    SPP container overview
diff --git a/docs/guides/tools/sppc/usecases.rst b/docs/guides/tools/sppc/usecases.rst
index 7fadf22..216c2bc 100644
--- a/docs/guides/tools/sppc/usecases.rst
+++ b/docs/guides/tools/sppc/usecases.rst
@@ -44,7 +44,7 @@ all of app container processes run on a single node.
 .. _figure_sppc_usecase_vhost:
 
 .. figure:: ../../images/tools/sppc/sppc_usecase_vhost.*
-    :width: 50%
+    :width: 58%
 
     Test of vhost PMD in a single node
 
@@ -285,7 +285,7 @@ as described in next sections.
 .. _figure_sppc_usecase_l2fwdpktgen:
 
 .. figure:: ../../images/tools/sppc/sppc_usecase_l2fwdpktgen.*
-    :width: 85%
+    :width: 95%
 
     Chainning pktgen and l2fwd
 
@@ -406,7 +406,7 @@ It is totally 7 lcores while the maximum number is 14.
 .. _figure_sppc_usecase_l2fwdpktgen_less:
 
 .. figure:: ../../images/tools/sppc/sppc_usecase_l2fwdpktgen_less.*
-    :width: 85%
+    :width: 95%
 
     Pktgen and l2fwd using less lcores
 
diff --git a/docs/guides/use_cases/spp_nfv.rst b/docs/guides/use_cases/spp_nfv.rst
index d9d922c..3e31508 100644
--- a/docs/guides/use_cases/spp_nfv.rst
+++ b/docs/guides/use_cases/spp_nfv.rst
@@ -64,7 +64,7 @@ patches as you defined.
 .. _figure_spp_nfv_as_l2fwd:
 
 .. figure:: ../images/setup/use_cases/spp_nfv_l2fwd.*
-   :width: 52%
+   :width: 60%
 
    spp_nfv as l2fwd
 
@@ -134,7 +134,7 @@ from ``phy:1`` to ``phy:0`` for ``nfv 2``.
 .. _figure_spp_two_nfv_as_l2fwd:
 
 .. figure:: ../images/setup/use_cases/spp_two_nfv_l2fwd.*
-   :width: 52%
+   :width: 60%
 
    Two spp_nfv as l2fwd
 
@@ -159,7 +159,7 @@ Patch ``phy:0`` to ``phy:0`` for ``nfv 1`` and
 .. _figure_spp_two_nfv_loopback:
 
 .. figure:: ../images/setup/use_cases/spp_two_nfv_loopback.*
-   :width: 52%
+   :width: 62%
 
    Two spp_nfv for loopback
 
@@ -233,7 +233,7 @@ Then, connect it with ``patch`` subcommand.
 .. _figure_spp_uni_directional_l2fwd:
 
 .. figure:: ../images/setup/use_cases/spp_unidir_l2fwd.*
-   :width: 52%
+   :width: 72%
 
    Uni-Directional l2fwd
 
@@ -296,7 +296,7 @@ Then, add ``ring:0`` and ``ring:1`` to ``nfv 2``.
 .. _figure_spp_bi_directional_l2fwd:
 
 .. figure:: ../images/setup/use_cases/spp_bidir_l2fwd.*
-   :width: 52%
+   :width: 72%
 
    Bi-Directional l2fwd
 
@@ -370,7 +370,7 @@ with ``nfv 2``.
 .. _figure_spp_uni_directional_l2fwd_vhost:
 
 .. figure:: ../images/setup/use_cases/spp_unidir_l2fwd_vhost.*
-   :width: 52%
+   :width: 72%
 
    Uni-Directional l2fwd with vhost
 
@@ -430,7 +430,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.*
-   :width: 50%
+   :width: 60%
 
    Rapture incoming packets
 
@@ -473,7 +473,7 @@ Then, add pcap PMD ``pcap:2`` to another ``spp_nfv``.
 .. _figure_spp_pcap_restoring:
 
 .. figure:: ../images/setup/use_cases/spp_pcap_restoring.*
-   :width: 52%
+   :width: 60%
 
    Restore dumped packets
 
-- 
2.7.4

  parent reply	other threads:[~2019-01-10  2:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10  2:10 [spp] [PATCH 0/8] Revise documentation ogawa.yasufumi
2019-01-10  2:10 ` [spp] [PATCH 1/8] docs: add desc of overview of SPP secondary ogawa.yasufumi
2019-01-10  2:10 ` [spp] [PATCH 2/8] docs: add desc of design of spp_nfv ogawa.yasufumi
2019-01-10  2:10 ` [spp] [PATCH 3/8] docs: add image of ports_fwd_array ogawa.yasufumi
2019-01-10  2:10 ` [spp] [PATCH 4/8] docs: add image of spp_nfv threads ogawa.yasufumi
2019-01-10  2:10 ` ogawa.yasufumi [this message]
2019-01-10  2:10 ` [spp] [PATCH 6/8] docs: resize font size in multi nodes example ogawa.yasufumi
2019-01-10  2:10 ` [spp] [PATCH 7/8] docs: resize font size in performance test ogawa.yasufumi
2019-01-10  2:10 ` [spp] [PATCH 8/8] docs: resize image of lb in sppc ogawa.yasufumi
2019-01-10 10:25 ` [spp] [PATCH v2 0/8] Revise documentation ogawa.yasufumi
2019-01-10 10:25   ` [spp] [PATCH v2 1/8] docs: add desc of overview of SPP secondary ogawa.yasufumi
2019-01-10 10:25   ` [spp] [PATCH v2 2/8] docs: add desc of design of spp_nfv ogawa.yasufumi
2019-01-10 10:25   ` [spp] [PATCH v2 3/8] docs: add image of ports_fwd_array ogawa.yasufumi
2019-01-10 10:25   ` [spp] [PATCH v2 4/8] docs: add image of spp_nfv threads ogawa.yasufumi
2019-01-10 10:25   ` [spp] [PATCH v2 5/8] docs: adjust size of images ogawa.yasufumi
2019-01-10 10:25   ` [spp] [PATCH v2 6/8] docs: resize font size in multi nodes example ogawa.yasufumi
2019-01-10 10:25   ` [spp] [PATCH v2 7/8] docs: resize font size in performance test ogawa.yasufumi
2019-01-10 10:25   ` [spp] [PATCH v2 8/8] docs: resize image of lb in sppc 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=1547086216-27422-6-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).