From: Richard Palethorpe <rpalethorpe@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3 0/6] cfs_bandwidth01 and CGroup API
Date: Wed, 02 Jun 2021 11:05:29 +0100 [thread overview]
Message-ID: <87eedkk2dy.fsf@suse.de> (raw)
In-Reply-To: <CAEemH2c2W1Z9W3dm2LoyMbtqJxtgZjEBHF8VDU3O1ZSJ2ZQmeA@mail.gmail.com>
Hello Li,
Li Wang <liwang@redhat.com> writes:
>> This adds a test scheduler test which uses the cpu controller.
>>
>> Also included are some additions and fixes to the CGroup API related
>> to the test.
>>
>> V3:
>> * Reverse order of writing cpu.cfs_period_us and cpu.cfs_quota_us to fix V1.
>> * Add may_have_waiters to indicate we should try waking and cleaning up
>> children during cleanup. At worst this can result in timeout warnings if there
>> are less than 9 children waiting.
>> Which is probably better than failing to cleanup the CGroups.
>
> I helped to test the patchset and push. Thanks~
Much thanks!
--
Thank you,
Richard.
prev parent reply other threads:[~2021-06-02 10:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 10:55 [LTP] [PATCH v3 0/6] cfs_bandwidth01 and CGroup API Richard Palethorpe
2021-06-01 10:55 ` [LTP] [PATCH v3 1/6] API/cgroups: Allow fetching of CGroup name Richard Palethorpe
2021-06-01 10:55 ` [LTP] [PATCH v3 2/6] API/cgroups: Remove obsolete function in API Richard Palethorpe
2021-06-01 10:55 ` [LTP] [PATCH v3 3/6] API/cgroups: Add cpu controller Richard Palethorpe
2021-06-01 10:55 ` [LTP] [PATCH v3 4/6] API/cgroups: Auto add controllers to subtree_control in new subgroup Richard Palethorpe
2021-06-01 10:55 ` [LTP] [PATCH v3 5/6] API/cgroups: tst_require fail gracefully with unknown controller Richard Palethorpe
2021-06-01 10:55 ` [LTP] [PATCH v3 6/6] sched/cgroup: Add cfs_bandwidth01 Richard Palethorpe
2021-06-02 7:02 ` [LTP] [PATCH v3 0/6] cfs_bandwidth01 and CGroup API Li Wang
2021-06-02 10:05 ` Richard Palethorpe [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=87eedkk2dy.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.