[dpdk-dev] [dpdk-stable] [PATCH] doc: removed typing mistake

David Marchand david.marchand at redhat.com
Thu Nov 26 12:01:51 CET 2020


On Wed, Sep 9, 2020 at 11:39 PM Muhammad Bilal <m.bilal at emumba.com> wrote:
>
> Here I have removed 'that' from the sentence to make it grammatically
> correct, as it seems to be a typing mistake
>
> Fixes: d0dff9ba445e ("doc: sample application user guide")
> Cc: bernard.iremonger at intel.com
>
> Signed-off-by: Muhammad Bilal <m.bilal at emumba.com>
> ---
>  doc/guides/prog_guide/multi_proc_support.rst | 2 +-
>  doc/guides/sample_app_ug/multi_process.rst   | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/doc/guides/prog_guide/multi_proc_support.rst b/doc/guides/prog_guide/multi_proc_support.rst
> index a84083b96..a0d71a81a 100644
> --- a/doc/guides/prog_guide/multi_proc_support.rst
> +++ b/doc/guides/prog_guide/multi_proc_support.rst
> @@ -136,7 +136,7 @@ can use).
>  Running Multiple Independent Groups of DPDK Applications
>  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> -In the same way that it is possible to run independent DPDK applications side- by-side on a single system,
> +In the same way, it is possible to run independent DPDK applications side- by-side on a single system,
>  this can be trivially extended to multi-process groups of DPDK applications running side-by-side.
>  In this case, the secondary processes must use the same ``--file-prefix`` parameter
>  as the primary process whose shared memory they are connecting to.
> diff --git a/doc/guides/sample_app_ug/multi_process.rst b/doc/guides/sample_app_ug/multi_process.rst
> index f2a79a639..87c703b83 100644
> --- a/doc/guides/sample_app_ug/multi_process.rst
> +++ b/doc/guides/sample_app_ug/multi_process.rst
> @@ -302,7 +302,7 @@ One additional enhancement in this sample application is that the server process
>  This eliminates the need for the client processes to have the portmask parameter passed into them on the command line,
>  as is done for the symmetric multi-process application, and therefore eliminates mismatched parameters as a potential source of errors.
>
> -In the same way that the server process is designed to be run as a primary process instance only,
> +In the same way, the server process is designed to be run as a primary process instance only,
>  the client processes are designed to be run as secondary instances only.
>  They have no code to attempt to create shared memory objects.
>  Instead, handles to all needed rings and memory pools are obtained via calls to rte_ring_lookup() and rte_mempool_lookup().

Sorry, but I don't see what is wrong with the original form.


-- 
David Marchand



More information about the dev mailing list