All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.com>
Cc: Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>,
	Joerg Vehlow <joerg.vehlow@aox-tech.de>,
	ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] memcg_subgroup_charge: Remove limiting of parent
Date: Tue, 14 Sep 2021 14:32:45 +0200	[thread overview]
Message-ID: <YUCWbfn/cm2Cr2U5@yuki> (raw)
Message-ID: <20210914123245.nQsZvJzZDZRpHXkmKuUnLhQvaLvVnCqa2VDVHv00WKg@z> (raw)
In-Reply-To: <20210914083444.23848-1-rpalethorpe@suse.com>

Hi!
> It is not important how much memory is assigned to the parent
> group. The stated purpose of the test is to check no memory is
> assigned to the child group.
> 
> Also add the usage stats for the memcg_process because it appears
> the test will fail because the starting memory counter already
> includes some buffer/cache on linux-next. I'm not sure this
> is exactly what happens, but displaying the stats might help.

Uff just found that there is a similar patch from Joerg as well:

http://patchwork.ozlabs.org/project/ltp/patch/20191106061808.67330-1-lkml@jv-coder.de/

Either way we should merge one of them to get this finally fixed.

-- 
Cyril Hrubis
chrubis@suse.cz

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

  reply	other threads:[~2021-09-14 12:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 22:27 [LTP] [PATCH] memcg: memcg_subgroup_charge.sh: Fix the parent memory limit Masayoshi Mizuma
2021-03-08  8:07 ` Joerg Vehlow
2021-09-14  8:34   ` [LTP] [PATCH] memcg_subgroup_charge: Remove limiting of parent Richard Palethorpe via ltp
2021-09-14  8:34     ` Richard Palethorpe via ltp
2021-09-14 12:32       ` Cyril Hrubis [this message]
2021-09-14 12:32         ` Cyril Hrubis
2021-09-20  5:20       ` Joerg Vehlow
2021-09-21 15:00         ` Cyril Hrubis

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=YUCWbfn/cm2Cr2U5@yuki \
    --to=chrubis@suse.cz \
    --cc=joerg.vehlow@aox-tech.de \
    --cc=ltp@lists.linux.it \
    --cc=m.mizuma@jp.fujitsu.com \
    --cc=rpalethorpe@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.