All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michal Koutný" <mkoutny@suse.com>
To: Tao Cui <cuitao@kylinos.cn>
Cc: tj@kernel.org, hannes@cmpxchg.org, cgroups@vger.kernel.org
Subject: Re: [PATCH] selftests: cgroup: Add basic tests for rdma controller
Date: Thu, 30 Apr 2026 19:59:49 +0200	[thread overview]
Message-ID: <afOT2cX2WOs0U05S@localhost.localdomain> (raw)
In-Reply-To: <20260430084310.80662-1-cuitao@kylinos.cn>

[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]

Hello.

On Thu, Apr 30, 2026 at 04:43:10PM +0800, Tao Cui <cuitao@kylinos.cn> wrote:
> +struct rdmacg_test {
> +	int (*fn)(const char *root);
> +	const char *name;
> +} tests[] = {
> +	T(test_rdmacg_max_read),
> +	T(test_rdmacg_max_write_nonexistent),
> +	T(test_rdmacg_max_write_invalid),
> +	T(test_rdmacg_max_device_limits),
> +	T(test_rdmacg_max_hierarchy),

IIUC, these are tests for proper parsing of the limits but not so useful
wrt RDMA controller (test_rdmacg_max_read has apparently little use).

I see that you try to work with a first found device -- if that's
available, it'd be good to have a test that checks whether respective
rdma.current-s respond to object allocations.


As I am looking at test_hugetlb_memcg.c that does only simple
testing of the .current would be sufficient, not sure how difficult
would be to implement a test for actual limit enforcement (but would be
nice too).

I.e. -- these would be good test to validate basic behavior of the
controller.

Thanks,
Michal

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 265 bytes --]

  reply	other threads:[~2026-04-30 17:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30  8:43 [PATCH] selftests: cgroup: Add basic tests for rdma controller Tao Cui
2026-04-30 17:59 ` Michal Koutný [this message]
2026-05-06  8:35   ` Tao Cui
2026-05-06 12:43     ` [PATCH v2] " Tao Cui
2026-05-07  1:43       ` [PATCH v3] " Tao Cui

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=afOT2cX2WOs0U05S@localhost.localdomain \
    --to=mkoutny@suse.com \
    --cc=cgroups@vger.kernel.org \
    --cc=cuitao@kylinos.cn \
    --cc=hannes@cmpxchg.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 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.