DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kefu Chai <tchaikov@gmail.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, Kefu Chai <tchaikov@gmail.com>
Subject: [dpdk-dev] [PATCH] doc/guides: add a missing word
Date: Mon, 18 Oct 2021 22:29:23 +0800	[thread overview]
Message-ID: <20211018142923.146430-1-tchaikov@gmail.com> (raw)

change from "how many segments each segment can have" to
"how many segments each segment list can have".

Signed-off-by: Kefu Chai <tchaikov@gmail.com>
---
 doc/guides/prog_guide/env_abstraction_layer.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst b/doc/guides/prog_guide/env_abstraction_layer.rst
index d124eb0e9a..29f6fefc48 100644
--- a/doc/guides/prog_guide/env_abstraction_layer.rst
+++ b/doc/guides/prog_guide/env_abstraction_layer.rst
@@ -204,8 +204,8 @@ variables:
 * ``RTE_MAX_MEMSEG_LISTS`` controls how many segment lists can DPDK have
 * ``RTE_MAX_MEM_MB_PER_LIST`` controls how much megabytes of memory each
   segment list can address
-* ``RTE_MAX_MEMSEG_PER_LIST`` controls how many segments each segment can
-  have
+* ``RTE_MAX_MEMSEG_PER_LIST`` controls how many segments each segment list
+  can have
 * ``RTE_MAX_MEMSEG_PER_TYPE`` controls how many segments each memory type
   can have (where "type" is defined as "page size + NUMA node" combination)
 * ``RTE_MAX_MEM_MB_PER_TYPE`` controls how much megabytes of memory each
-- 
2.33.0


             reply	other threads:[~2021-10-18 14:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 14:29 Kefu Chai [this message]
2021-11-26 13:51 ` David Marchand

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=20211018142923.146430-1-tchaikov@gmail.com \
    --to=tchaikov@gmail.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@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).