mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Vernet <void@manifault.com>
To: Tejun Heo <tj@kernel.org>
Cc: lizefan.x@bytedance.com, hannes@cmpxchg.org,
	cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-team@fb.com
Subject: Re: [PATCH 0/4] cgroup: Introduce cpu controller test suite
Date: Fri, 22 Apr 2022 05:32:27 -0700	[thread overview]
Message-ID: <20220422123227.gtirbsygpjek3iss@dev0025.ash9.facebook.com> (raw)
In-Reply-To: <YmHY3t9UC2/zDyMz@slm.duckdns.org>

Hi Tejun,

On Thu, Apr 21, 2022 at 12:21:18PM -1000, Tejun Heo wrote:
> * Can you please repost w/ Ingo and Peterz cc'd?

Will do, I'll cc them on v2.

> * Maybe cpucg instead of cgcpu?

Agreed, that seems more intuitive. I'll change it in v2.

> * Single level testing is great but extending the case to cover deeper
>   nesting level would be great. ie. a test case with multi level tree w/
>   both under and over provisioned parts in the tree.

This sounds like a great idea. I have another patch set that I was planning
to send out which adds a few more testcases. I can include some testcases
in that set which validate more complicated nesting setups.

Thanks,
David

  reply	other threads:[~2022-04-22 12:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19 21:32 David Vernet
2022-04-19 21:32 ` [PATCH 1/4] cgroup: Add new test_cpu.c test suite in cgroup selftests David Vernet
2022-04-19 21:32 ` [PATCH 2/4] cgroup: Add test_cgcpu_stats() testcase to cgroup cpu selftests David Vernet
2022-04-19 21:32 ` [PATCH 3/4] cgroup: Add test_cgcpu_weight_overprovisioned() testcase David Vernet
2022-04-19 21:32 ` [PATCH 4/4] cgroup: Add test_cgcpu_weight_underprovisioned() testcase David Vernet
2022-04-21 22:21 ` [PATCH 0/4] cgroup: Introduce cpu controller test suite Tejun Heo
2022-04-22 12:32   ` David Vernet [this message]
2022-04-22 17:33 David Vernet
2022-04-22 17:48 ` Tejun Heo
2022-04-22 17:50   ` Peter Zijlstra
2022-04-22 18:40 ` 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=20220422123227.gtirbsygpjek3iss@dev0025.ash9.facebook.com \
    --to=void@manifault.com \
    --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=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
all inboxes | Powered by JetHome®