DPDK patches and discussions
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Shepard Siegel <shepard.siegel@atomicrules.com>,
	 Ed Czeck <ed.czeck@atomicrules.com>,
	John Miller <john.miller@atomicrules.com>
Subject: Re: [PATCH] doc/ark: replace word segregation
Date: Tue, 4 Apr 2023 00:06:16 +0100	[thread overview]
Message-ID: <CAMw=ZnTT0=U0j+-=cemCLTKpoS6qnDTGnHFEukePOGPGf4e_4Q@mail.gmail.com> (raw)
In-Reply-To: <20230402225356.104666-1-stephen@networkplumber.org>

On Sun, 2 Apr 2023 at 23:54, Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> The word "segregation" brings up troubling memorys.
> Instead, use the term seperation which is what DPDK flow docs use.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
>  doc/guides/nics/ark.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/guides/nics/ark.rst b/doc/guides/nics/ark.rst
> index de8fbbccc304..ab08214df1e2 100644
> --- a/doc/guides/nics/ark.rst
> +++ b/doc/guides/nics/ark.rst
> @@ -353,7 +353,7 @@ Supported Features
>
>  * Dynamic ARK PMD extensions
>  * Dynamic per-queue MBUF (re)sizing up to 32KB
> -* SR-IOV, VF-based queue-segregation
> +* SR-IOV, VF-based queue-seperation

Did you mean 'separation' by any chance?

  parent reply	other threads:[~2023-04-03 23:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-02 22:53 Stephen Hemminger
2023-04-03  5:31 ` Tyler Retzlaff
2023-05-17 18:31   ` Ferruh Yigit
2023-04-03 23:06 ` Luca Boccassi [this message]
2023-04-04  2:15   ` Stephen Hemminger

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='CAMw=ZnTT0=U0j+-=cemCLTKpoS6qnDTGnHFEukePOGPGf4e_4Q@mail.gmail.com' \
    --to=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=ed.czeck@atomicrules.com \
    --cc=john.miller@atomicrules.com \
    --cc=shepard.siegel@atomicrules.com \
    --cc=stephen@networkplumber.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).