All of lore.kernel.org
 help / color / mirror / Atom feed
From: pavrampu <pavrampu@linux.ibm.com>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v8] memcg/memcontrol05: add cgroup v2 task migration charge accounting test
Date: Fri, 13 Nov 2026 11:18:57 +0530	[thread overview]
Message-ID: <8a045cf3096d2293c7e35cd001566de6@linux.ibm.com> (raw)
In-Reply-To: <avSp8HV3he2he28I@localhost.localdomain>

On 2026-11-11 23:17, Michal Koutný wrote:
> Hello.
> 
> On Sun, Nov 08, 2026 at 11:50:34AM +0530, Pavithra
> <pavrampu@linux.ibm.com> wrote:
>> Verify that in cgroup v2, memory charges remain pinned to the cgroup
>> that allocated them when a task migrates, and that new allocations 
>> after
>> migration are charged to the destination cgroup.
> 
> The staticness of memory charges is "non-functional" feature of cgroup
> v2. Could you explain more the real word motivation behind this case?
> 
> (Each such testcase is subject to noise and it's good to understand
> what/why are the expectations.)
> 
> Thanks,
> Michal

  Hi Michal,

Thanks for the inputs, basically trying to migrate 
testcases/kernel/controllers/memctl/ test to cgroupv2 Depending on its 
applicability to v2, we can determine whether to proceed with this 
patch.

Thanks,
Pavithra

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2026-11-13  5:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-08  6:20 [LTP] [PATCH v8] memcg/memcontrol05: add cgroup v2 task migration charge accounting test Pavithra
2026-11-08  6:48 ` [LTP] " linuxtestproject.agent
2026-11-11 17:47 ` [LTP] [PATCH v8] " Michal Koutný via ltp
2026-11-13  5:48   ` pavrampu [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=8a045cf3096d2293c7e35cd001566de6@linux.ibm.com \
    --to=pavrampu@linux.ibm.com \
    --cc=ltp@lists.linux.it \
    --cc=mkoutny@suse.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: 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.