From: Cyril Hrubis <chrubis@suse.cz>
To: Jan Stancek <jstancek@redhat.com>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] getrusage03: skip on small RAM system
Date: Mon, 7 Feb 2022 14:16:21 +0100 [thread overview]
Message-ID: <YgEbpTni5ID6d/bs@yuki> (raw)
In-Reply-To: <CAASaF6ytd7ROq_S48NnYWY4-VU+nGjX7NTcgM5aGQG6G0rh_OQ@mail.gmail.com>
Hi!
> > Signed-off-by: Li Wang <liwang@redhat.com>
>
> Acked-by: Jan Stancek <jstancek@redhat.com>
>
> This should fix the immediate failure, just wondering,
> would there be any downside of replacing that TBROK with TCONF?
I guess that we may end up in a state where the test would TCONF on
every run and it would end up being ingnored.
Can't we just change the consume_mb to lock the memory with mlock() in
the consume_mb() instead? As long as we add the check for a free memory
it should be fine I guess.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-02-07 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 4:04 [LTP] [PATCH] getrusage03: skip on small RAM system Li Wang
2022-02-07 7:40 ` Petr Vorel
2022-02-07 10:08 ` Li Wang
2022-02-07 11:12 ` Petr Vorel
2022-02-07 9:16 ` Jan Stancek
2022-02-07 12:09 ` Li Wang
2022-02-07 13:16 ` Cyril Hrubis [this message]
2022-02-08 3:27 ` Li Wang
2022-02-07 13:19 ` Cyril Hrubis
2022-02-08 3:21 ` Li Wang
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=YgEbpTni5ID6d/bs@yuki \
--to=chrubis@suse.cz \
--cc=jstancek@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox