public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] madvise06: wait a bit after madvise() call
Date: Fri, 22 Jul 2016 07:02:41 -0400 (EDT)	[thread overview]
Message-ID: <1001938980.7344214.1469185361447.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1364997364.18740114.1469184887166.JavaMail.zimbra@redhat.com>



----- Original Message -----
> From: "Chunyu Hu" <chuhu@redhat.com>
> To: "Jan Stancek" <jstancek@redhat.com>
> Cc: ltp@lists.linux.it, "Chunyu Hu" <chuhu@redhat.com>
> Sent: Friday, 22 July, 2016 12:54:47 PM
> Subject: Re: [LTP] [PATCH] madvise06: wait a bit after madvise() call
> > > 
> > > Attached is approach v3, which sets up memory cgroup:
> > > - memory.limit_in_bytes is 128M
> > > - we allocate 512M
> > > - as consequence ~384M should be swapped while system should still have
> > >   plenty of free memory, which should be available for cache
> 
> I use the same host to test your V3, didn't reproduce the false positive
> issue.
> It skipped the test when the swap space is so large successfully. So great
> V3! Thanks.
> I guess if we got the V4, that's must be tricky, but seems no need now?

I posted v3 just now. I reduced allocated size to 400M, so it should
run also on systems as small as 1GB RAM. Other than that, it contains
feedback from Li and some additional checks so it TCONFs on older kernels
which don't have all /proc and memory cgroup knobs.

Regards,
Jan

> 
> [root@dhcp-chuhu mem]# ./b
> tst_test.c:701: INFO: Timeout per run is 300s
> b.c:73: INFO: dropping caches
> b.c:175: INFO: SwapCached (before madvise): 78688
> b.c:188: INFO: SwapCached (after madvise): 486628
> b.c:190: PASS: Regression test pass
> 
> Summary:
> passed   1
> failed   0
> skipped  0
> warnings 0
> [root@dhcp-chuhu mem]# ./b
> tst_test.c:701: INFO: Timeout per run is 300s
> b.c:73: INFO: dropping caches
> b.c:78: CONF: System RAM is too small, skip test
> 
> Summary:
> passed   0
> failed   0
> skipped  0
> warnings 0
> 
> 
> 
> > > Regards,
> > > Jan
> > > 
> > > 
> > 
> > --
> > Regards,
> > Chunyu Hu
> > 
> > 
> > --
> > Mailing list info: https://lists.linux.it/listinfo/ltp
> > 
> 
> --
> Regards,
> Chunyu Hu
> 
> 

      reply	other threads:[~2016-07-22 11:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18 13:37 [LTP] [PATCH] madvise06: wait a bit after madvise() call Jan Stancek
2016-07-18 14:03 ` Cyril Hrubis
2016-07-18 14:22   ` Jan Stancek
2016-07-18 14:49     ` Cyril Hrubis
2016-07-19  5:58 ` Li Wang
2016-07-19  6:56   ` Jan Stancek
2016-07-19  8:57     ` Li Wang
2016-07-20 14:37       ` Jan Stancek
2016-07-21  5:33         ` Li Wang
2016-07-21 10:31         ` Chunyu Hu
2016-07-21 11:02           ` Li Wang
2016-07-21 14:23             ` Jan Stancek
2016-07-22  3:46               ` Li Wang
2016-07-22  6:59                 ` Jan Stancek
2016-07-22 10:49               ` Chunyu Hu
2016-07-22 10:54                 ` Chunyu Hu
2016-07-22 11:02                   ` Jan Stancek [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=1001938980.7344214.1469185361447.JavaMail.zimbra@redhat.com \
    --to=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