From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3] Add process_madvise01 test
Date: Fri, 1 Sep 2023 14:53:58 +0200 [thread overview]
Message-ID: <ZPHe5jRwRI9ZGJI0@yuki> (raw)
In-Reply-To: <7058a129-f1b8-4a52-a6b2-7c0fd6643dee@suse.com>
Hi!
> >> BTW I wonder if we should add 'vmstat' or 'cat /proc/meminfo' to ver_linux.
> > cat /proc/meminfo sounds like a good idea.
> >
> Maybe do we need a flag in tst_test to check if swap is available or
> not? Something similar to .min_mem_avail.
Sounds reasonable to me, that way we would get the information
propagated into metadata as well. Feel free to send a patch.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2023-09-01 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 7:38 [LTP] [PATCH v3] Add process_madvise01 test Andrea Cervesato
2023-08-30 10:45 ` Cyril Hrubis
2023-09-01 10:37 ` Petr Vorel
2023-09-01 12:16 ` Cyril Hrubis
2023-09-01 12:31 ` Petr Vorel
2023-09-01 12:36 ` Cyril Hrubis
2023-09-01 12:52 ` Andrea Cervesato via ltp
2023-09-01 12:53 ` Cyril Hrubis [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=ZPHe5jRwRI9ZGJI0@yuki \
--to=chrubis@suse.cz \
--cc=andrea.cervesato@suse.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