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 13:32:29 +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> <20140523043918 dot GA404 at ubuntu> <20140523052635 dot GO507 at brightrain dot aerifal dot cx>
On Fri, May 23, 2014 at 01:26:35AM -0400, Rich Felker wrote:
> They are the same physical pages, so I don't see how you can drop one
> without dropping the other.
When the virtual memory area specified is huge, hopefully there are
many pmd pages will get dropped. Even some of the pud will get
> RSS is not "accountable memory". It's largely meaningless, because it
> includes memory that can be dropped at any time (without a need to
> save it to swap). Defining a process's memory usage in a meaningful
> way is difficult, but dirty pages, commit charge, and total RW mapping
> sizes are more likely to be useful metrics than RSS is.
But it's one the most important element that OOM killer considers.