From: Richard Palethorpe <rpalethorpe@suse.de>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] set_mempolicy01: cancel the limit of maximum runtime
Date: Wed, 28 Dec 2022 10:21:38 +0000 [thread overview]
Message-ID: <87pmc3st8g.fsf@suse.de> (raw)
In-Reply-To: <CAEemH2eCfzyTggCu9F0BEanen2aN=zzaB9f3WwMZB+3JDJMypw@mail.gmail.com>
Hello,
Li Wang <liwang@redhat.com> writes:
> On Tue, Dec 20, 2022 at 10:15 PM Cyril Hrubis <chrubis@suse.cz> wrote:
>
>> Hi!
>> > It needs more time for running on multiple numa nodes system.
>> > Here propose to cancel the limit of max_runtime.
>> >
>> > ========= test log on 16 nodes system =========
>> > ...
>> > set_mempolicy01.c:80: TPASS: child: Node 15 allocated 16
>> > tst_numa.c:25: TINFO: Node 0 allocated 0 pages
>> > tst_numa.c:25: TINFO: Node 1 allocated 0 pages
>> > tst_numa.c:25: TINFO: Node 2 allocated 0 pages
>> > tst_numa.c:25: TINFO: Node 3 allocated 0 pages
>> > tst_numa.c:25: TINFO: Node 4 allocated 0 pages
>> > tst_numa.c:25: TINFO: Node 5 allocated 0 pages
>> > tst_numa.c:25: TINFO: Node 6 allocated 0 pages
>> > tst_numa.c:25: TINFO: Node 7 allocated 0 pages
>> > tst_numa.c:25: TINFO: Node 8 allocated 0 pages
>> > tst_numa.c:25: TINFO: Node 9 allocated 0 pages
>> > tst_numa.c:25: TINFO: Node 10 allocated 0 pages
>> > tst_numa.c:25: TINFO: Node 11 allocated 0 pages
>> > tst_numa.c:25: TINFO: Node 12 allocated 0 pages
>> > tst_numa.c:25: TINFO: Node 13 allocated 0 pages
>> > tst_numa.c:25: TINFO: Node 14 allocated 0 pages
>> > tst_numa.c:25: TINFO: Node 15 allocated 16 pages
>> > set_mempolicy01.c:80: TPASS: parent: Node 15 allocated 16
>> >
>> > Summary:
>> > passed 393210
>> > failed 0
>> > broken 0
>> > skipped 0
>> > warnings 0
>> >
>> > real 6m15.147s
>> > user 0m33.641s
>> > sys 0m44.553s
>>
>> Can't we just set the default to 30 minutes or something large enough?
>>
>
> Yes, I thought about a fixed larger value before, but seems the test
> time go increased extremely faster when the test matrix doubled.
>
> I don't have a system with more than 32 nodes to check if 30mins
> enough, so I guess probably canceling the limitation like what we
> did for oom tests would make sense, that timeout value depends
> on real system configurations.
IMO, this is what the timeout multiplier is for. So if you have a
computer with 512 CPUs or a tiny embedded device, you can adjust the
timeouts upwards.
The default timeouts are for workstations, commodity servers and
VMs. Although I suppose as this is a NUMA test the average machine will
be bigger, but 32 nodes on a physical machine would be 128-512 CPUs?
>
>
> --
> Regards,
> Li Wang
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-12-28 10:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 5:45 [LTP] [PATCH] set_mempolicy01: cancel the limit of maximum runtime Li Wang
2022-12-20 14:16 ` Cyril Hrubis
2022-12-21 1:59 ` Li Wang
2022-12-28 10:21 ` Richard Palethorpe [this message]
2022-12-29 3:04 ` Li Wang
2022-12-30 3:21 ` [LTP] [PATCH v2] set_mempolicy01: adjust the maximum runtime base on nodes Li Wang
2023-01-02 8:41 ` Petr Vorel
2023-01-09 10:07 ` Richard Palethorpe
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=87pmc3st8g.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
/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.