public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Richard Palethorpe <rpalethorpe@suse.de>
To: Hongchen Zhang <zhanghongchen@loongson.cn>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] cpuset_memory_spread: set lowerlimit according to pagesize
Date: Wed, 30 Aug 2023 08:45:12 +0100	[thread overview]
Message-ID: <87r0nlhsh7.fsf@suse.de> (raw)
In-Reply-To: <20230830064250.31904-1-zhanghongchen@loongson.cn>

Hello,

Hongchen Zhang <zhanghongchen@loongson.cn> writes:

> When I test the cpuset_memory_spread case,this case FAIL too often.
> After dig into the code, I find out that the fowlloing things trigger
> the FAIL:
> 1) random events,the probability is very small and can be ignored
> 2) get_meminfo which before send signal to test_pid
> 3) account_memsinfo before result_check
>
> About 2) and 3), we can increase the value of lowerlimit to keep
> the result as SUCCESS.
>
> After discussing with Richard, we all agree to use the following
> formula to calculate the lowerlimit:
> lowerlimit(kb) = pagesize(byte) * 512 / 1024
>
> Signed-off-by: Hongchen Zhang <zhanghongchen@loongson.cn>
> ---
>  .../cpuset_memory_spread_testset.sh                    | 10 +++++++++-
>  1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git
> a/testcases/kernel/controllers/cpuset/cpuset_memory_spread_test/cpuset_memory_spread_testset.sh
> b/testcases/kernel/controllers/cpuset/cpuset_memory_spread_test/cpuset_memory_spread_testset.sh
> index e2767ef05..f7230a4ea 100755
> --- a/testcases/kernel/controllers/cpuset/cpuset_memory_spread_test/cpuset_memory_spread_testset.sh
> +++ b/testcases/kernel/controllers/cpuset/cpuset_memory_spread_test/cpuset_memory_spread_testset.sh
> @@ -38,7 +38,15 @@ nr_mems=$N_NODES
>  # on which it is running. The other nodes' slab space has littler change.(less
>  # than 1000 kb).
>  upperlimit=10000
> -lowerlimit=2000
> +
> +# set lowerlimit according to pagesize
> +# pagesize(bytes)  | lowerlimit(kb)
> +# ------------------------------------
> +#  4096            | 2048
> +#  16384           | 8192
> +
> +PAGE_SIZE=`tst_getconf PAGESIZE`
> +lowerlimit=$((PAGE_SIZE * 512 / 1024))
>  
>  cpus_all="$(seq -s, 0 $((nr_cpus-1)))"
>  mems_all="$(seq -s, 0 $((nr_mems-1)))"
>
> base-commit: 020f3985a5ca86c8bbece27eef8fb0315a10463e

If we don't set the upperlimit what happens if we have 64Kb pages and
the lowerlimit > upperlimit?

-- 
Thank you,
Richard.

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

  reply	other threads:[~2023-08-30  7:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30  6:42 [LTP] [PATCH v2] cpuset_memory_spread: set lowerlimit according to pagesize Hongchen Zhang
2023-08-30  7:45 ` Richard Palethorpe [this message]
2023-08-30 10:46   ` Hongchen Zhang
2023-08-31  8:27     ` Richard Palethorpe
2023-08-31  8:51       ` Hongchen Zhang

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=87r0nlhsh7.fsf@suse.de \
    --to=rpalethorpe@suse.de \
    --cc=ltp@lists.linux.it \
    --cc=zhanghongchen@loongson.cn \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox