From: Stephen Hemminger <stephen@networkplumber.org>
To: <pbhagavatula@marvell.com>
Cc: <jerinj@marvell.com>, <dev@dpdk.org>
Subject: Re: [PATCH v2] doc: update Linux core isolation guide
Date: Tue, 17 May 2022 11:22:24 -0700 [thread overview]
Message-ID: <20220517112224.6e17f80b@hermes.local> (raw)
In-Reply-To: <20220517180856.1139-1-pbhagavatula@marvell.com>
On Tue, 17 May 2022 23:38:55 +0530
<pbhagavatula@marvell.com> wrote:
> +
> +.. Note::
> +
> + For more fine grained control over resource management and performance tuning one can look
> + into ``Linux cgroups``.
Please provide a better link than just search terms:
Suggestions:
Cgroups uses cpusets.
https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/cpusets.html
Systemd provides standard API for system service contiainers.
https://www.freedesktop.org/software/systemd/man/systemd.exec.html
- See CPUAffinity
See Also:
https://man7.org/linux/man-pages/man7/cpuset.7.html
https://www.suse.com/c/cpu-isolation-practical-example-part-5/
https://www.rcannings.com/systemd-core-isolation/
next prev parent reply other threads:[~2022-05-17 18:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 7:24 [PATCH] " Pavan Nikhilesh
2022-05-02 20:17 ` Stephen Hemminger
2022-05-10 15:50 ` [EXT] " Pavan Nikhilesh Bhagavatula
2022-05-17 18:08 ` [PATCH v2] " pbhagavatula
2022-05-17 18:22 ` Stephen Hemminger [this message]
2022-05-17 18:32 ` [EXT] " Pavan Nikhilesh Bhagavatula
2022-05-17 19:59 ` [PATCH v3] " pbhagavatula
2022-06-02 7:47 ` Jerin Jacob
2022-07-11 20:59 ` Thomas Monjalon
2022-10-31 11:57 ` [PATCH v4] " pbhagavatula
2022-11-15 15:57 ` 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=20220517112224.6e17f80b@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@marvell.com \
/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).