From: Roman Gushchin <roman.gushchin@linux.dev> To: Andrew Morton <akpm@linux-foundation.org> Cc: Tejun Heo <tj@kernel.org>, David Vernet <void@manifault.com>, linux-kernel@vger.kernel.org, linux-mm@kvack.org, cgroups@vger.kernel.org, Johannes Weiner <hannes@cmpxchg.org>, Michal Hocko <mhocko@kernel.org>, Shakeel Butt <shakeelb@google.com>, Roman Gushchin <roman.gushchin@linux.dev> Subject: [PATCH 0/4] mm: memcg kselftests fixes Date: Thu, 14 Apr 2022 17:01:29 -0700 [thread overview] Message-ID: <20220415000133.3955987-1-roman.gushchin@linux.dev> (raw) I'm resending two memcg kselftests fixes, which I first posted in 2019 [1], however they didn't go anywhere. I've rechecked them and they're are both still actual, even though there were new regressions introduced since that, so not all tests are passing now. I know that David Vernet (cc'ed) is working on fixing (some of) them, so hopefully he'll post more fixes soon. I believe it's better for such patches to go through mm and cgroup trees (and mailing lists), where there are better chances for them to be properly reviewed, so adding corresponding entries to the MAINTAINERS file to make it obvious. 1: https://lore.kernel.org/lkml/20191203165758.GA607734@chrisdown.name/T/ Roman Gushchin (4): kselftests: memcg: update the oom group leaf events test kselftests: memcg: speed up the memory.high test MAINTAINERS: add corresponding kselftests to cgroup entry MAINTAINERS: add corresponding kselftests to memcg entry MAINTAINERS | 3 +++ tools/testing/selftests/cgroup/test_memcontrol.c | 7 ++++--- 2 files changed, 7 insertions(+), 3 deletions(-) -- 2.35.1
WARNING: multiple messages have this Message-ID (diff)
From: Roman Gushchin <roman.gushchin-fxUVXftIFDnyG1zEObXtfA@public.gmane.org> To: Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> Cc: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>, David Vernet <void-gq6j2QGBifHby3iVrkZq2A@public.gmane.org>, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org, cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>, Michal Hocko <mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>, Shakeel Butt <shakeelb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>, Roman Gushchin <roman.gushchin-fxUVXftIFDnyG1zEObXtfA@public.gmane.org> Subject: [PATCH 0/4] mm: memcg kselftests fixes Date: Thu, 14 Apr 2022 17:01:29 -0700 [thread overview] Message-ID: <20220415000133.3955987-1-roman.gushchin@linux.dev> (raw) I'm resending two memcg kselftests fixes, which I first posted in 2019 [1], however they didn't go anywhere. I've rechecked them and they're are both still actual, even though there were new regressions introduced since that, so not all tests are passing now. I know that David Vernet (cc'ed) is working on fixing (some of) them, so hopefully he'll post more fixes soon. I believe it's better for such patches to go through mm and cgroup trees (and mailing lists), where there are better chances for them to be properly reviewed, so adding corresponding entries to the MAINTAINERS file to make it obvious. 1: https://lore.kernel.org/lkml/20191203165758.GA607734-6Bi1550iOqEnzZ6mRAm98g@public.gmane.org/T/ Roman Gushchin (4): kselftests: memcg: update the oom group leaf events test kselftests: memcg: speed up the memory.high test MAINTAINERS: add corresponding kselftests to cgroup entry MAINTAINERS: add corresponding kselftests to memcg entry MAINTAINERS | 3 +++ tools/testing/selftests/cgroup/test_memcontrol.c | 7 ++++--- 2 files changed, 7 insertions(+), 3 deletions(-) -- 2.35.1
next reply other threads:[~2022-04-15 0:01 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-15 0:01 Roman Gushchin [this message] 2022-04-15 0:01 ` [PATCH 0/4] mm: memcg kselftests fixes Roman Gushchin 2022-04-15 0:01 ` [PATCH 1/4] kselftests: memcg: update the oom group leaf events test Roman Gushchin 2022-04-15 14:08 ` David Vernet 2022-04-15 14:08 ` David Vernet 2022-04-15 15:59 ` Roman Gushchin 2022-04-15 15:59 ` Roman Gushchin 2022-04-15 0:01 ` [PATCH 2/4] kselftests: memcg: speed up the memory.high test Roman Gushchin 2022-04-15 0:01 ` Roman Gushchin 2022-04-15 14:11 ` David Vernet 2022-04-15 14:11 ` David Vernet 2022-04-15 0:01 ` [PATCH 3/4] MAINTAINERS: add corresponding kselftests to cgroup entry Roman Gushchin 2022-04-15 0:01 ` Roman Gushchin 2022-04-21 19:25 ` Tejun Heo 2022-04-21 19:25 ` Tejun Heo 2022-04-21 20:16 ` Roman Gushchin 2022-04-21 20:16 ` Roman Gushchin 2022-04-15 0:01 ` [PATCH 4/4] MAINTAINERS: add corresponding kselftests to memcg entry Roman Gushchin 2022-04-15 0:01 ` Roman Gushchin
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=20220415000133.3955987-1-roman.gushchin@linux.dev \ --to=roman.gushchin@linux.dev \ --cc=akpm@linux-foundation.org \ --cc=cgroups@vger.kernel.org \ --cc=hannes@cmpxchg.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mhocko@kernel.org \ --cc=shakeelb@google.com \ --cc=tj@kernel.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: linkBe 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.