From: Michal Hocko <mhocko@kernel.org>
To: Houssem Daoud <houssem.daoud@polymtl.ca>
Cc: 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: Wed, 13 Jul 2016 15:19:05 +0200 [thread overview]
Message-ID: <20160713131905.GA28731@dhcp22.suse.cz> (raw)
In-Reply-To: <d8e2130c-5a1c-bd6c-0f79-6b17bb6da645@polymtl.ca>
[CC ext/jbd experts]
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)
>
> --
> 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>
--
Michal Hocko
SUSE Labs
--
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>
next prev parent reply other threads:[~2016-07-13 13:19 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 [this message]
2016-07-14 15:08 ` Jan Kara
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=20160713131905.GA28731@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=houssem.daoud@polymtl.ca \
--cc=jack@suse.cz \
--cc=linux-mm@kvack.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