From: Peter Newman <peternewman@google.com>
To: reinette.chatre@intel.com, fenghua.yu@intel.com
Cc: Babu.Moger@amd.com, bp@alien8.de, dave.hansen@linux.intel.com,
eranian@google.com, gupasani@google.com, hpa@zytor.com,
james.morse@arm.com, linux-kernel@vger.kernel.org,
mingo@redhat.com, skodak@google.com, tony.luck@intel.com,
tglx@linutronix.de, x86@kernel.org,
Peter Newman <peternewman@google.com>
Subject: [PATCH v3 0/3] x86/resctrl: Implement rename to help move containers' tasks
Date: Wed, 25 Jan 2023 11:13:31 +0100 [thread overview]
Message-ID: <20230125101334.1069060-1-peternewman@google.com> (raw)
Hi Reinette, Fenghua,
This patch series implements the solution Reinette suggested in the
earlier RFD thread[1] for the problem of moving a container's tasks to a
different control group on systems that don't provide enough CLOSIDs to
give every container its own control group.
This patch series assumes that a MON group's CLOSID can simply be
changed to that of a new parent CTRL_MON group. This is allowed on Intel
and AMD, but not MPAM implementations. While we (Google) only foresee
needing this functionality on Intel and AMD systems, this series should
hopefully be a good starting point for supporting MPAM.
Thanks!
-Peter
Updates:
v3: use revised task CLOSID/RMID update IPI sync method from [3]
v2: reworded change logs based on what I've learned from review comments
in another patch series[2]
[v1] https://lore.kernel.org/lkml/20221115154515.952783-1-peternewman@google.com/
[v2] https://lore.kernel.org/lkml/20221129120149.1035444-1-peternewman@google.com/
[1] https://lore.kernel.org/lkml/7b09fb62-e61a-65b9-a71e-ab725f527ded@intel.com/
[2] https://lore.kernel.org/lkml/54e50a9b-268f-2020-f54c-d38312489e2f@intel.com/
[3] https://lore.kernel.org/lkml/20221220161123.432120-1-peternewman@google.com/
Peter Newman (3):
x86/resctrl: Factor rdtgroup lock for multi-file ops
x86/resctrl: Factor work to update task CLOSID/RMID
x86/resctrl: Implement rename op for mon groups
arch/x86/kernel/cpu/resctrl/rdtgroup.c | 170 ++++++++++++++++++-------
1 file changed, 126 insertions(+), 44 deletions(-)
base-commit: 2241ab53cbb5cdb08a6b2d4688feb13971058f65
--
2.39.1.405.gd4c25cc71f-goog
next reply other threads:[~2023-01-25 10:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 10:13 Peter Newman [this message]
2023-01-25 10:13 ` [PATCH v3 1/3] x86/resctrl: Factor rdtgroup lock for multi-file ops Peter Newman
2023-02-10 23:21 ` Reinette Chatre
2023-01-25 10:13 ` [PATCH v3 2/3] x86/resctrl: Factor work to update task CLOSID/RMID Peter Newman
2023-01-25 10:13 ` [PATCH v3 3/3] x86/resctrl: Implement rename op for mon groups Peter Newman
2023-02-10 23:21 ` Reinette Chatre
2023-03-02 14:26 ` Peter Newman
2023-03-02 22:26 ` Reinette Chatre
2023-03-03 15:10 ` Peter Newman
2023-03-03 19:05 ` Reinette Chatre
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=20230125101334.1069060-1-peternewman@google.com \
--to=peternewman@google.com \
--cc=Babu.Moger@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=eranian@google.com \
--cc=fenghua.yu@intel.com \
--cc=gupasani@google.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=skodak@google.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®