linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Michal Hocko <mhocko@kernel.org>
Cc: Houssem Daoud <houssem.daoud@polymtl.ca>,
	linux-mm@kvack.org, Jan Kara <jack@suse.cz>,
	Theodore Ts'o <tytso@mit.edu>
Subject: Re: Unexpected growth of the LRU inactive list
Date: Thu, 14 Jul 2016 17:08:24 +0200	[thread overview]
Message-ID: <20160714150824.GI13151@quack2.suse.cz> (raw)
In-Reply-To: <20160713131905.GA28731@dhcp22.suse.cz>

On Wed 13-07-16 15:19:05, Michal Hocko wrote:
> [CC ext/jbd experts]

Thanks.

> On Wed 13-07-16 01:48:57, Houssem Daoud wrote:
> > Hi,
> > 
> > I was testing the filesystem performance of my system using the following
> > script:
> > 
> > #!/bin/bash
> > while true;
> > do
> > dd if=/dev/zero of=output.dat  bs=100M count=1
> > done
> > 
> > I noticed that after some time, all the physical memory is consumed by the
> > LRU inactive list and only 120 MB are left to the system.
> > /proc/meminfo shows the following information:
> > MemTotal: 4021820 Kb
> > MemFree: 121912 Kb
> > Active: 1304396 Kb
> > Inactive: 2377124 Kb
> > 
> > The evolution of memory utilization over time is available in this link:
> > http://secretaire.dorsal.polymtl.ca/~hdaoud/ext4_journal_meminfo.png
> > 
> > With the help of a kernel tracer, I found that most of the pages in the
> > inactive list are created by the ext4 journal during a truncate operation.
> > The call stack of the allocation is:
> > [
> > __alloc_pages_nodemask
> > alloc_pages_current
> > __page_cache_alloc
> > find_or_create_page
> > __getblk
> > jbd2_journal_get_descriptor_buffer
> > jbd2_journal_commit_transaction
> > kjournald2
> > kthread
> > ]
> > 
> > I can't find an explanation why the LRU is growing while we are just writing
> > to the same file again and again. I know that the philosophy of memory
> > management in Linux is to use the available memory as much as possible, but
> > what is the need of keeping truncated pages in the LRU if we know that they
> > are not even accessible ?
> > 
> > Thanks !
> > 
> > ps: My system is running kernel 4.3 with ext4 filesystem (journal mode)

This problem should be fixed by commit bc23f0c8d7cc "jbd2: Fix unreclaimed
pages after truncate in data=journal mode" which was merged into 4.4.

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2016-07-14 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-13  5:48 Houssem Daoud
2016-07-13 13:19 ` Michal Hocko
2016-07-14 15:08   ` Jan Kara [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=20160714150824.GI13151@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=houssem.daoud@polymtl.ca \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=tytso@mit.edu \
    /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