This is the mail archive of the
mailing list for the glibc project.
Re: Propose to Use madvise API on Runtime Loader
- From: lin zuojian <manjian2006 at gmail dot com>
- To: Rich Felker <dalias at libc dot org>
- Cc: libc-alpha at sourceware dot org
- Date: Fri, 23 May 2014 12:39:18 +0800
- Subject: Re: Propose to Use madvise API on Runtime Loader
- Authentication-results: sourceware.org; auth=none
- References: <20140523012855 dot GC14217 at ubuntu> <20140523025730 dot GL507 at brightrain dot aerifal dot cx> <20140523031242 dot GA24355 at ubuntu> <20140523040146 dot GM507 at brightrain dot aerifal dot cx> <20140523042133 dot GA29872 at ubuntu> <20140523043129 dot GN507 at brightrain dot aerifal dot cx>
> I'm aware of this, but is it dropped or not? First you claimed the
> resident memory drops from the madvise call, but then you claimed it
> doesn't drop from the page cache. I think you need to explain this
> more clearly if there's going to be a discussion of the merits of your
It really drops the page tables, which alwarys belong to a process
, not cache or other kernel usage.That would save some pages.
But it does not drop from the page cache.
And the accoutable memory, e.g. RSS, of a process drops.
The page reclaiming process will reclaim these pages earlier.
Because it access eariler.