From: Daniel Micay <danielmicay@gmail.com>
To: Andy Lutomirski <luto@amacapital.net>, Minchan Kim <minchan@kernel.org>
Cc: Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Michal Hocko <mhocko@suse.cz>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Rik van Riel <riel@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Linux API <linux-api@vger.kernel.org>, Jason Evans <je@fb.com>,
Shaohua Li <shli@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
yalin.wang2010@gmail.com, Mel Gorman <mgorman@suse.de>
Subject: Re: [PATCH v2 01/13] mm: support madvise(MADV_FREE)
Date: Wed, 4 Nov 2015 00:53:42 -0500 [thread overview]
Message-ID: <56399D66.5010606@gmail.com> (raw)
In-Reply-To: <56399CA5.8090101@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
> In the common case it will be passed many pages by the allocator. There
> will still be a layer of purging logic on top of MADV_FREE but it can be
> much thinner than the current workarounds for MADV_DONTNEED. So the
> allocator would still be coalescing dirty ranges and only purging when
> the ratio of dirty:clean pages rises above some threshold. It would be
> able to weight the largest ranges for purging first rather than logic
> based on stuff like aging as is used for MADV_DONTNEED.
I would expect that jemalloc would just start putting the dirty ranges
into the usual pair of red-black trees (with coalescing) and then doing
purging starting from the largest spans to get back down below whatever
dirty:clean ratio it's trying to keep. Right now, it has all lots of
other logic to deal with this since each MADV_DONTNEED call results in
lots of zeroing and then page faults.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-04 5:54 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 1:25 [PATCH v2 00/13] MADV_FREE support Minchan Kim
2015-11-04 1:25 ` [PATCH v2 01/13] mm: support madvise(MADV_FREE) Minchan Kim
2015-11-04 2:16 ` Sergey Senozhatsky
2015-11-04 23:39 ` Minchan Kim
2015-11-05 3:41 ` Sergey Senozhatsky
2015-11-04 2:29 ` Sergey Senozhatsky
2015-11-04 23:40 ` Minchan Kim
2015-11-04 3:41 ` Andy Lutomirski
2015-11-04 5:50 ` Daniel Micay
2015-11-04 5:53 ` Daniel Micay [this message]
2015-11-04 6:04 ` Daniel Micay
2015-11-04 18:23 ` Andy Lutomirski
2015-11-04 22:05 ` Daniel Micay
2015-11-05 18:17 ` Shaohua Li
2015-11-05 20:13 ` Daniel Micay
2015-11-05 20:14 ` Daniel Micay
2015-11-05 0:13 ` Minchan Kim
2015-11-05 0:42 ` Andy Lutomirski
2015-11-05 0:56 ` Minchan Kim
2015-11-05 1:29 ` Andy Lutomirski
2015-11-05 1:48 ` Minchan Kim
2015-11-04 20:00 ` Shaohua Li
2015-11-04 21:16 ` Daniel Micay
2015-11-04 21:29 ` Daniel Micay
2015-11-04 21:43 ` Andy Lutomirski
2015-11-05 1:33 ` Minchan Kim
2015-11-05 1:37 ` Minchan Kim
2015-12-01 22:30 ` John Stultz
2015-11-04 1:25 ` [PATCH v2 02/13] mm: define MADV_FREE for some arches Minchan Kim
2015-11-04 1:25 ` [PATCH v2 03/13] arch: uapi: asm: mman.h: Let MADV_FREE have same value for all architectures Minchan Kim
2015-11-04 1:25 ` [PATCH v2 04/13] mm: free swp_entry in madvise_free Minchan Kim
2015-11-04 1:25 ` [PATCH v2 05/13] mm: move lazily freed pages to inactive list Minchan Kim
2015-11-04 1:26 ` [PATCH v2 06/13] mm: clear PG_dirty to mark page freeable Minchan Kim
2015-11-04 1:26 ` [PATCH v2 07/13] mm: mark stable page dirty in KSM Minchan Kim
2015-11-04 1:26 ` [PATCH v2 08/13] x86: add pmd_[dirty|mkclean] for THP Minchan Kim
2015-11-04 1:26 ` [PATCH v2 09/13] sparc: " Minchan Kim
2015-11-04 1:26 ` [PATCH v2 10/13] powerpc: " Minchan Kim
2015-11-04 1:26 ` [PATCH v2 11/13] arm: add pmd_mkclean " Minchan Kim
2015-11-04 1:26 ` [PATCH v2 12/13] arm64: " Minchan Kim
2015-11-04 1:26 ` [PATCH v2 13/13] mm: don't split THP page when syscall is called Minchan Kim
2015-12-05 11:10 ` [PATCH v2 00/13] MADV_FREE support Pavel Machek
2015-12-05 15:51 ` Daniel Micay
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=56399D66.5010606@gmail.com \
--to=danielmicay@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=je@fb.com \
--cc=kirill@shutemov.name \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=minchan@kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=riel@redhat.com \
--cc=shli@kernel.org \
--cc=yalin.wang2010@gmail.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;
as well as URLs for NNTP newsgroup(s).