On Tue, Jul 07, 2026 at 01:07:40PM +0200, Kamil Konieczny wrote: > Hi Thadeu, > On 2026-07-02 at 10:00:58 -0300, Thadeu Lima de Souza Cascardo wrote: > > Based on the work of Thomas Hellström to test dmem.max eviction, add a test > > for dmem.current usage after allocations and setting dmem.max. > > > > Create a dmem cgroup, allocate close to capacity (or at most 4GiB), check > > current usage is within a small slack of the expected allocation. Then, > > set max to a small value and check allocations and current usage are > > limited to the max set. Set max to 0, then check no allocations are > > allowed and current usage is also within the slack. After each allocation, > > release memory and check current usage has gone down. > > > > Signed-off-by: Thadeu Lima de Souza Cascardo <[email protected]> > > --- > > tests/dmem_cgroups.c | 245 +++++++++++++++++++++++++++++++++++++++++++ > > Why two tests? dmesm_cgropus and cgroups_dmem? > Why not only one? This is confusing. > > Regards, > Kamil
Agreed. This is the result of cgroups_dmem being present in the original patchset and the other test being Xe specific. The Xe specific test is now replaced by what I initially called drv_dmem_cgroups, but I ended up renaming dmem_cgroups. I will merge them all into cgroups_dmem and send a v4. Thanks. Cascardo.
