From: Xishi Qiu <qiuxishi@huawei.com>
To: Michal Hocko <mhocko@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
Mel Gorman <mgorman@techsingularity.net>,
Andrea Arcangeli <aarcange@redhat.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
zhong jiang <zhongjiang@huawei.com>,
Yisheng Xie <xieyisheng1@huawei.com>,
"Liyong (Q)" <liyong1@huawei.com>
Subject: [RFC] mm: why active file + inactive file is larger than cached + buffers?
Date: Fri, 25 May 2018 18:05:23 +0800 [thread overview]
Message-ID: <5B07DFE3.2030804@huawei.com> (raw)
Hi, I find the active file + inactive file is larger than cached + buffers, about 5G,
and can not free it by "echo 3 > /proc/sys/vm/drop_caches"
The meminfo shows that the mapped is also very small, so maybe some get the page? (e.g. get_user_pages())
Then it will dec the count of NR_FILE_PAGES when delete from page cache, but because of the count,
the page can not delete from lru, so left active file + inactive file so large, right?
MemTotal: 61528660 kB
MemFree: 48678936 kB
MemAvailable: 53657348 kB
Buffers: 10832 kB
Cached: 640340 kB
SwapCached: 0 kB
Active: 5933664 kB
Inactive: 588968 kB
Active(anon): 1022200 kB
Inactive(anon): 533248 kB
Active(file): 4911464 kB
Inactive(file): 55720 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 10952 kB
Writeback: 0 kB
AnonPages: 980572 kB
Mapped: 85464 kB
Shmem: 581580 kB
Slab: 343480 kB
SReclaimable: 264632 kB
SUnreclaim: 78848 kB
KernelStack: 8368 kB
PageTables: 18012 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 28667176 kB
Committed_AS: 4144064 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 265848 kB
VmallocChunk: 34359417096 kB
HardwareCorrupted: 0 kB
AnonHugePages: 688128 kB
HugePages_Total: 4
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 1048576 kB
DirectMap4k: 182112 kB
DirectMap2M: 11294720 kB
DirectMap1G: 51380224 kB
reply other threads:[~2018-05-25 10:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5B07DFE3.2030804@huawei.com \
--to=qiuxishi@huawei.com \
--cc=aarcange@redhat.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liyong1@huawei.com \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=vbabka@suse.cz \
--cc=xieyisheng1@huawei.com \
--cc=zhongjiang@huawei.com \
/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