From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] madvise06: wait a bit after madvise() call
Date: Thu, 21 Jul 2016 19:02:00 +0800 [thread overview]
Message-ID: <20160721110159.GA13274@gmail.com> (raw)
In-Reply-To: <597691787.18542977.1469097118207.JavaMail.zimbra@redhat.com>
On Thu, Jul 21, 2016 at 06:31:58AM -0400, Chunyu Hu wrote:
> >
> > If you still have the setup, can you try how reliable is this approach?
>
> I also had a try on my desktop. I copied the file as a.c and compiled it in ltp.
> Result is that if the sys is fresh with low Cache, it can pass rightly. But if
> the Cache is before exhausted, it can hit failure, as the thresh_hold is too
> large to get there. Just FYI.
Yes, Chunyu ran failed the case with his destop(uptime more than 30days) at first,
after rebooting it could be PASS.
We guess the reason is the current usage of SwapCached are too large and
madvise_willneed() could not shift the memory(swapout) into swapcache.
To verify this image we incresed SwapCached by another program(background)
then it always get failures like that. Probably it's still hitting the
situations we discussed before:
2. It pending I/O with short dely.
3. kernel ignoring the request for unknow reasons.
Regards,
Li Wang
next prev parent reply other threads:[~2016-07-21 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 [this message]
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
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=20160721110159.GA13274@gmail.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox