diff mbox series

[v4,21/27] doc: fix incorrect reference to master process

Message ID	20200701202359.17006-22-stephen@networkplumber.org (mailing list archive)
State	Superseded, archived
Delegated to:	Thomas Monjalon
Headers	From: Stephen Hemminger <stephen@networkplumber.org> To: dev@dpdk.org Cc: Stephen Hemminger <stephen@networkplumber.org>, bernard.iremonger@intel.com Date: Wed, 1 Jul 2020 13:23:53 -0700 Message-Id: <20200701202359.17006-22-stephen@networkplumber.org> In-Reply-To: <20200701202359.17006-1-stephen@networkplumber.org> References: <20200604210200.25405-1-stephen@networkplumber.org> <20200701202359.17006-1-stephen@networkplumber.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-dev] [PATCH v4 21/27] doc: fix incorrect reference to master process Precedence: list Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org>
Series	Replace references to master and slave \| [v4,00/27] Replace references to master and slave [v4,01/27] eal: rename terms used for DPDK lcores [v4,02/27] kni: fix reference to master/slave process [v4,03/27] bbdev: rename master to initial lcore [v4,04/27] librte_power: change reference to rte_master_lcore [v4,05/27] drivers: replace master/slave terminology [v4,06/27] examples/distributor: rename master to initial [v4,07/27] examples/bond: replace references to master lcore [v4,08/27] examples/ethtool-app: replace references to slave with worker [v4,09/27] examples/ip_pipeline: replace references to master_lcore [v4,10/27] examples/qos_{meter/sched}: replace references to master lcore [v4,11/27] examples/l3fwd: replace references to master lcore [v4,12/27] examples/l2fwd: replace references to master lcore [v4,13/27] examples/multi_process: replace references to master lcore [v4,14/27] examples/performance-thread: replace reference to master lcore [v4,15/27] examples/ptpclient: replace references to master lcore [v4,16/27] examples/ipcsec-secgw: replace references to master lcore [v4,17/27] examples: replace reference to master lcore [v4,18/27] app/test-pmd: change references to master/slave [v4,19/27] test-eventdev: replace references to slave with worker lcores [v4,20/27] app/test: replace refernces to master/slave [v4,21/27] doc: fix incorrect reference to master process [v4,22/27] doc: update references to master/slave lcore in documentation [v4,23/27] app/pdump: replace references to master/slave lcore [v4,24/27] app/test-XXX: replace reference to master/slave [v4,25/27] eal: mark old naming as deprecated [v4,26/27] memif: replace master/slave with server/client [v4,27/27] vhost: rename SLAVE to CLIENT

Checks

Context	Check	Description
ci/checkpatch	success	coding style OK
ci/Intel-compilation	fail	Compilation issues

Commit Message

Stephen Hemminger July 1, 2020, 8:23 p.m. UTC

Correct terminolgy here is primary process.
This is a bug in original doc.

Fixes: fc1f2750a3ec ("doc: programmers guide")
Cc: bernard.iremonger@intel.com
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 doc/guides/prog_guide/thread_safety_dpdk_functions.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Comments

Burakov, Anatoly July 15, 2020, 1:24 p.m. UTC | #1

On 01-Jul-20 9:23 PM, Stephen Hemminger wrote:
> Correct terminolgy here is primary process.
> This is a bug in original doc.
> 
> Fixes: fc1f2750a3ec ("doc: programmers guide")
> Cc: bernard.iremonger@intel.com
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---

Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>

diff mbox series

Patch

diff --git a/doc/guides/prog_guide/thread_safety_dpdk_functions.rst b/doc/guides/prog_guide/thread_safety_dpdk_functions.rst
index 0f539db2b869..5618e25e47fb 100644
--- a/doc/guides/prog_guide/thread_safety_dpdk_functions.rst
+++ b/doc/guides/prog_guide/thread_safety_dpdk_functions.rst
@@ -61,8 +61,8 @@  rather than subsequently in the forwarding threads.
 However, the DPDK performs checks to ensure that libraries are only initialized once.
 If initialization is attempted more than once, an error is returned.
 
-In the multi-process case, the configuration information of shared memory will only be initialized by the master process.
-Thereafter, both master and secondary processes can allocate/release any objects of memory that finally rely on rte_malloc or memzones.
+In the multi-process case, the configuration information of shared memory will only be initialized by the primary process.
+Thereafter, both primary and secondary processes can allocate/release any objects of memory that finally rely on rte_malloc or memzones.
 
 Interrupt Thread
 ----------------