mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: David Vernet <void@manifault.com>
Cc: lizefan.x@bytedance.com, hannes@cmpxchg.org,
	cgroups@vger.kernel.org, peterz@infradead.org, mingo@redhat.com,
	linux-kernel@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH 1/5] cgroup: Adding test_cpucg_nested_weight_overprovisioned() testcase
Date: Mon, 25 Apr 2022 07:28:17 -1000	[thread overview]
Message-ID: <YmbaMZfBJp3Ngd/6@slm.duckdns.org> (raw)
In-Reply-To: <20220423123053.2982931-1-void@manifault.com>

On Sat, Apr 23, 2022 at 05:30:50AM -0700, David Vernet wrote:
> The cgroup cpu controller tests in
> tools/testing/selftests/cgroup/test_cpu.c have some testcases that validate
> the expected behavior of setting cpu.weight on cgroups, and then hogging
> CPUs. What is still missing from the suite is a testcase that validates
> nested cgroups. This patch adds test_cpucg_nested_weight_overprovisioned(),
> which validates that a parent's cpu.weight will override its children if
> they overcommit a host, and properly protect any sibling groups of that
> parent.
> 
> Signed-off-by: David Vernet <void@manifault.com>

Applied 1-5 to cgroup/for-5.19.

Thanks.

-- 
tejun

      parent reply	other threads:[~2022-04-25 17:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-23 12:30 David Vernet
2022-04-23 12:30 ` [PATCH 2/5] cgroup: Add test_cpucg_nested_weight_underprovisioned() testcase David Vernet
2022-04-23 12:30 ` [PATCH 3/5] cgroup: Add test_cpucg_max() testcase David Vernet
2022-04-23 12:30 ` [PATCH 4/5] Add test_cpucg_max_nested() testcase David Vernet
2022-04-23 12:30 ` [PATCH 5/5] cgroup: Add config file to cgroup selftest suite David Vernet
2022-04-25 17:28 ` Tejun Heo [this message]

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=YmbaMZfBJp3Ngd/6@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=kernel-team@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan.x@bytedance.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=void@manifault.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
all inboxes | Powered by JetHome®