From: Daniel Micay <danielmicay@gmail.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Minchan Kim <minchan@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
linux-api@vger.kernel.org, Hugh Dickins <hughd@google.com>,
zhangyanfei@cn.fujitsu.com, Rik van Riel <riel@redhat.com>,
Mel Gorman <mgorman@suse.de>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Jason Evans <je@fb.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Michal Hocko <mhocko@suse.cz>,
yalin.wang2010@gmail.com, Shaohua Li <shli@kernel.org>,
"Wang, Yalin" <Yalin.Wang@sonymobile.com>
Subject: Re: [PATCH 5/8] mm: move lazily freed pages to inactive list
Date: Wed, 4 Nov 2015 18:49:54 -0500 [thread overview]
Message-ID: <563A99A2.6010708@gmail.com> (raw)
In-Reply-To: <563A9681.3070102@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
> From a user perspective, it doesn't depend on swap. It's just slower
> without swap because it does what MADV_DONTNEED does. The current
> implementation can be dropped in where MADV_DONTNEED was previously used.
It just wouldn't replace existing layers of purging logic until that
edge case is fixed and it gains better THP integration.
It's already a very useful API with significant performance wins over
MADV_DONTNEED, so it will be useful. The only risk involved in landing
it is that a better feature might come along. Worst case scenario being
that the kernel ends up with a synonym for MADV_DONTNEED (but I think
there will still be a use case for this even if a pinning/unpinning API
existed, as this is more precise).
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-04 23:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 7:01 [PATCH 0/8] MADV_FREE support Minchan Kim
2015-10-30 7:01 ` [PATCH 1/8] mm: support madvise(MADV_FREE) Minchan Kim
2015-10-30 16:49 ` Shaohua Li
2015-11-03 0:10 ` Minchan Kim
2015-10-30 7:01 ` [PATCH 2/8] mm: define MADV_FREE for some arches Minchan Kim
2015-10-30 7:01 ` [PATCH 3/8] arch: uapi: asm: mman.h: Let MADV_FREE have same value for all architectures Minchan Kim
2015-11-02 0:08 ` Hugh Dickins
2015-11-03 2:32 ` Minchan Kim
2015-11-03 2:36 ` Minchan Kim
2015-11-03 3:36 ` David Miller
2015-11-03 4:31 ` Minchan Kim
2015-10-30 7:01 ` [PATCH 4/8] mm: free swp_entry in madvise_free Minchan Kim
2015-10-30 12:28 ` Michal Hocko
2015-11-03 0:53 ` Minchan Kim
2015-10-30 7:01 ` [PATCH 5/8] mm: move lazily freed pages to inactive list Minchan Kim
2015-10-30 17:22 ` Shaohua Li
2015-11-03 0:52 ` Minchan Kim
2015-11-04 8:15 ` Michal Hocko
2015-11-04 17:53 ` Shaohua Li
2015-11-04 18:20 ` Shaohua Li
2015-11-05 1:11 ` Minchan Kim
2015-11-05 1:03 ` Minchan Kim
2015-11-04 20:55 ` Johannes Weiner
2015-11-04 21:48 ` Daniel Micay
2015-11-04 22:55 ` Johannes Weiner
2015-11-04 23:36 ` Daniel Micay
2015-11-04 23:49 ` Daniel Micay [this message]
2015-10-30 7:01 ` [PATCH 6/8] mm: lru_deactivate_fn should clear PG_referenced Minchan Kim
2015-10-30 12:47 ` Michal Hocko
2015-11-03 1:10 ` Minchan Kim
2015-11-04 8:22 ` Michal Hocko
2015-10-30 7:01 ` [PATCH 7/8] mm: clear PG_dirty to mark page freeable Minchan Kim
2015-10-30 12:55 ` Michal Hocko
2015-10-30 7:01 ` [PATCH 8/8] mm: mark stable page dirty in KSM Minchan Kim
2015-11-01 4:51 ` [PATCH 0/8] MADV_FREE support David Rientjes
2015-11-01 6:29 ` Daniel Micay
2015-11-03 2:23 ` Minchan Kim
2015-11-04 20:19 ` David Rientjes
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=563A99A2.6010708@gmail.com \
--to=danielmicay@gmail.com \
--cc=Yalin.Wang@sonymobile.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=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 \
--cc=zhangyanfei@cn.fujitsu.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).