From: David Vernet <void@manifault.com>
To: Tejun Heo <tj@kernel.org>
Cc: peterz@infradead.org, mingo@redhat.com, cgroups@vger.kernel.org,
lizefan.x@bytedance.com, hannes@cmpxchg.org, mkoutny@suse.com,
kernel-team@meta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/7] sched: Make cpu_shares_read_u64() use tg_weight()
Date: Thu, 8 Aug 2024 12:38:18 -0500 [thread overview]
Message-ID: <20240808173818.GC6223@maniforge> (raw)
In-Reply-To: <20240808002550.731248-5-tj@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
On Wed, Aug 07, 2024 at 02:25:26PM -1000, Tejun Heo wrote:
> Move tg_weight() upward and make cpu_shares_read_u64() use it too. This
> makes the weight retrieval shared between cgroup v1 and v2 paths and will be
> used to implement cgroup support for sched_ext.
>
> No functional changes.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
Acked-by: David Vernet <void@manifault.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-08-08 17:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 0:25 [PATCHSET sched_ext/for-6.12] sched_ext: Add cgroup support Tejun Heo
2024-08-08 0:25 ` [PATCH 1/7] cgroup: Implement cgroup_show_cftypes() Tejun Heo
2024-08-20 14:38 ` Michal Koutný
2024-08-26 18:35 ` Tejun Heo
2024-08-08 0:25 ` [PATCH 2/7] sched: Expose css_tg() Tejun Heo
2024-08-08 0:25 ` [PATCH 3/7] sched: Enumerate CPU cgroup file types Tejun Heo
2024-08-08 0:25 ` [PATCH 4/7] sched: Make cpu_shares_read_u64() use tg_weight() Tejun Heo
2024-08-08 17:38 ` David Vernet [this message]
2024-08-08 0:25 ` [PATCH 5/7] sched: Introduce CONFIG_GROUP_SCHED_WEIGHT Tejun Heo
2024-08-08 0:25 ` [PATCH 6/7] sched_ext: Add cgroup support Tejun Heo
2024-08-08 0:25 ` [PATCH 7/7] sched_ext: Add a cgroup scheduler which uses flattened hierarchy 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=20240808173818.GC6223@maniforge \
--to=void@manifault.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=mingo@redhat.com \
--cc=mkoutny@suse.com \
--cc=peterz@infradead.org \
--cc=tj@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