From: Chris Edwards <chris.edwards@otago.ac.nz>
To: Johannes Weiner <hannes@cmpxchg.org>, Michal Hocko <mhocko@kernel.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Paging out when free memory is low but not exhausted (and available memory remains high)
Date: Tue, 28 Jan 2020 07:19:57 +0000 [thread overview]
Message-ID: <1580195997590.47770@otago.ac.nz> (raw)
In-Reply-To: <1580187538078.61819@otago.ac.nz>
[-- Attachment #1: Type: text/plain, Size: 531 bytes --]
A further update: I'm seeing what looks like the same paging-out behaviour on an Ubuntu 18.04.2 LTS system I have access to (Dell Optiplex 9020, Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz, 16 GiB RAM). Kernel version:
4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
vmstat output is attached for the following timeline:
1580195040 run stress
1580195050 run dd
1580195090 drop caches
1580195110 drop caches
So this may be longer-standing than I originally thought.
--
Chris
[-- Attachment #2: vmstat_Ubuntu_4.15.0-74-generic.tar.gz --]
[-- Type: application/gzip, Size: 17254 bytes --]
next prev parent reply other threads:[~2020-01-28 7:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 0:40 Paging out when free memory is low but not exhausted (and available memory remains high) Chris Edwards
2020-01-23 12:31 ` Michal Hocko
2020-01-24 5:43 ` Chris Edwards
2020-01-24 10:04 ` Michal Hocko
2020-01-24 10:28 ` Michal Hocko
2020-01-27 10:06 ` Johannes Weiner
2020-01-28 3:22 ` Chris Edwards
2020-01-28 4:58 ` Chris Edwards
2020-01-28 7:19 ` Chris Edwards [this message]
2020-01-29 11:36 ` Chris Edwards
2020-01-29 13:39 ` Michal Hocko
2020-01-29 16:39 ` Johannes Weiner
2020-02-02 22:56 ` Chris Edwards
2020-02-10 8:50 ` Michal Hocko
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=1580195997590.47770@otago.ac.nz \
--to=chris.edwards@otago.ac.nz \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).