From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Waiman Long <longman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Zefan Li <lizefan.x-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org>,
Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
Jonathan Corbet <corbet-T1hC0tSOHrs@public.gmane.org>,
Shuah Khan <shuah-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kselftest-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Juri Lelli <juri.lelli-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Valentin Schneider
<vschneid-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Frederic Weisbecker
<frederic-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [RFC PATCH 0/5] cgroup/cpuset: A new "isolcpus" paritition
Date: Fri, 14 Apr 2023 06:54:05 -1000 [thread overview]
Message-ID: <ZDmFLfII8EUX_ocY@slm.duckdns.org> (raw)
In-Reply-To: <226cb2da-e800-6531-4e57-cbf991022477-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Thu, Apr 13, 2023 at 09:22:19PM -0400, Waiman Long wrote:
> I now have a slightly different idea of how to do that. We already have an
> internal cpumask for partitioning - subparts_cpus. I am thinking about
> exposing it as cpuset.cpus.reserve. The current way of creating
> subpartitions will be called automatic reservation and require a direct
> parent/child partition relationship. But as soon as a user write anything to
> it, it will break automatic reservation and require manual reservation going
> forward.
>
> In that way, we can keep the old behavior, but also support new use cases. I
> am going to work on that.
I'm not sure I fully understand the proposed behavior but it does sound more
quirky.
Thanks.
--
tejun
next prev parent reply other threads:[~2023-04-14 16:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 15:37 [RFC PATCH 0/5] cgroup/cpuset: A new "isolcpus" paritition Waiman Long
2023-04-12 19:28 ` Tejun Heo
[not found] ` <1ce6a073-e573-0c32-c3d8-f67f3d389a28@redhat.com>
2023-04-12 20:22 ` Tejun Heo
2023-04-12 20:33 ` Waiman Long
2023-04-13 0:03 ` Tejun Heo
2023-04-13 0:26 ` Waiman Long
[not found] ` <cd4c3f92-4a01-e636-7390-8c6a3d0cfe6c-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2023-04-13 0:33 ` Tejun Heo
2023-04-13 0:55 ` Waiman Long
[not found] ` <1b8d9128-d076-7d37-767d-11d6af314662-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2023-04-13 1:17 ` Tejun Heo
2023-04-13 1:55 ` Waiman Long
[not found] ` <9862da55-5f41-24c3-f3bb-4045ccf24b2e-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2023-04-14 1:22 ` Waiman Long
[not found] ` <226cb2da-e800-6531-4e57-cbf991022477-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2023-04-14 16:54 ` Tejun Heo [this message]
2023-04-14 17:29 ` Waiman Long
2023-04-14 17:34 ` Tejun Heo
2023-04-14 17:38 ` Waiman Long
2023-04-14 19:06 ` Waiman Long
2023-05-02 18:01 ` Michal Koutný
2023-05-02 21:26 ` Waiman Long
2023-05-02 22:27 ` Michal Koutný
2023-05-04 3:01 ` Waiman Long
[not found] ` <deb7b684-3d7c-b3ae-7b36-5b7ba2dd8001-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2023-05-05 16:03 ` Tejun Heo
[not found] ` <ZFUo5IYAIwTEKR4_-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org>
2023-05-05 16:25 ` Waiman Long
2023-05-08 1:03 ` Waiman Long
2023-05-22 19:49 ` Tejun Heo
2023-05-28 21:18 ` Waiman Long
2023-06-05 18:03 ` Tejun Heo
[not found] ` <ZH4jfmypOXGJPu0D-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org>
2023-06-05 20:00 ` Waiman Long
2023-06-05 20:27 ` Tejun Heo
2023-06-06 2:47 ` Waiman Long
[not found] ` <a2220c9f-7a8d-da82-ecc0-b39f3807408c-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2023-06-06 19:58 ` Tejun Heo
[not found] ` <ZH-P7X_yjnVfhy7b-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org>
2023-06-06 20:11 ` Waiman Long
2023-06-06 20:13 ` Tejun Heo
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=ZDmFLfII8EUX_ocY@slm.duckdns.org \
--to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=corbet-T1hC0tSOHrs@public.gmane.org \
--cc=frederic-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=juri.lelli-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kselftest-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan.x-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org \
--cc=longman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=shuah-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=vschneid-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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