linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Chris Edwards <chris.edwards@otago.ac.nz>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
	Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: Paging out when free memory is low but not exhausted (and available memory remains high)
Date: Fri, 24 Jan 2020 11:28:10 +0100	[thread overview]
Message-ID: <20200124102810.GQ29276@dhcp22.suse.cz> (raw)
In-Reply-To: <20200124100423.GP29276@dhcp22.suse.cz>

On Fri 24-01-20 11:04:25, Michal Hocko wrote:
[...]
> $ awk '{diff=$1-prev; if (prev&&diff) printf "%d %d %d\n", NR, $1, diff; prev=$1}' pswpout
> 30 392136 2000
> 31 395513 3377
> 32 399132 3619
> 33 403101 3969
> 34 407211 4110
> 35 410812 3601
> 36 414120 3308
> 37 418119 3999
> 38 422116 3997
> 39 424154 2038
> 40 428110 3956
> 
> So the swappout started around 18:25:00

Sorry, this should have been 18:25:29
$ sed '1,29d' vmstat-log.txt | head -n1
time 18:25:29

I hope I haven't misprocessed other data but a quick check suggests that
s ok.
-- 
Michal Hocko
SUSE Labs


  reply	other threads:[~2020-01-24 10:28 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 [this message]
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
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=20200124102810.GQ29276@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=chris.edwards@otago.ac.nz \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.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).