DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>, <dev@dpdk.org>
Subject: Re: [PATCH 1/2] doc/eal: add doc entry for service core list flag
Date: Thu, 26 Jun 2025 15:36:10 +0200	[thread overview]
Message-ID: <14688ff6-54c8-480b-bb3e-22e6f30f011c@intel.com> (raw)
In-Reply-To: <20250624133409.550372-2-bruce.richardson@intel.com>

On 6/24/2025 3:34 PM, Bruce Richardson wrote:
> In the list of EAL arguments, only the "-s" flag for service cores was
> documented. Add an entry for the "-S" one too, which takes a core list
> instead of a core mask.
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
>   doc/guides/linux_gsg/eal_args.include.rst | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/doc/guides/linux_gsg/eal_args.include.rst b/doc/guides/linux_gsg/eal_args.include.rst
> index 359721eb6a..6ee79877c1 100644
> --- a/doc/guides/linux_gsg/eal_args.include.rst
> +++ b/doc/guides/linux_gsg/eal_args.include.rst
> @@ -79,6 +79,11 @@ Lcore-related options
>   
>       Hexadecimal bitmask of cores to be used as service cores.
>   
> +*   ``-S <service core list>``
> +
> +    List of cores to be used as service cores.
> +
> +
>   Device-related options
>   ~~~~~~~~~~~~~~~~~~~~~~
>   

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

-- 
Thanks,
Anatoly

  reply	other threads:[~2025-06-26 13:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24 13:34 [PATCH 0/2] use core lists not masks in documentation Bruce Richardson
2025-06-24 13:34 ` [PATCH 1/2] doc/eal: add doc entry for service core list flag Bruce Richardson
2025-06-26 13:36   ` Burakov, Anatoly [this message]
2025-06-24 13:34 ` [PATCH 2/2] doc: use core lists rather than masks in guides Bruce Richardson
2025-06-26 13:40   ` Burakov, Anatoly

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=14688ff6-54c8-480b-bb3e-22e6f30f011c@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=bruce.richardson@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).