From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [PATCH 1/2] doc: add note about CPU 0
Date: Mon, 29 Jul 2024 21:59:11 +0200 [thread overview]
Message-ID: <2868191.Y6S9NjorxK@thomas> (raw)
In-Reply-To: <20240718184326.21375-1-stephen@networkplumber.org>
18/07/2024 20:43, Stephen Hemminger:
> On Linux (and probably BSD), CPU 0 can not be fully isolated
> because it receives timer interrupts and is used for other
> kernel related functions. The DPDK documentation should
> be updated to tell users to avoid polling on that CPU.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
> +.. note::
> +
> + It is not recommended to use CPU core 0 for DPDK polling applications
> + because it can not be isolated from other system and kernel activity.
Indent should be 3 spaces.
> For example, if a given CPU has 0-7 cores
> -and DPDK applications are to run on logical cores 2, 4 and 6,
> -the following should be added to the kernel parameter list:
> +and DPDK applications are to run on logical cores 2, 4 and 6.
> +The following should be added to the kernel parameter list:
I think it was better as 1 sentence with the comma.
next prev parent reply other threads:[~2024-07-29 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 18:43 Stephen Hemminger
2024-07-18 18:43 ` [PATCH 2/2] doc: remove use of -n 4 option in documentation Stephen Hemminger
2024-07-19 8:15 ` Bruce Richardson
2024-07-19 13:37 ` Jack Bond-Preston
2024-07-29 19:59 ` Thomas Monjalon [this message]
2024-07-31 4:38 ` [PATCH v2 1/2] doc: add note about CPU 0 Stephen Hemminger
2024-07-31 4:38 ` [PATCH v2 2/2] doc: remove use of -n 4 option in documentation Stephen Hemminger
2024-07-31 8:16 ` Thomas Monjalon
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=2868191.Y6S9NjorxK@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--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).