From: Andrew Morton <akpm@linux-foundation.org>
To: Minchan Kim <minchan@kernel.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Rik van Riel <riel@redhat.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Dave Hansen <dave.hansen@intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Minkyung Kim <minkyung88@lge.com>
Subject: Re: [PATCH v5 6/7] mm: Support address range reclaim
Date: Tue, 21 May 2013 17:33:32 -0700 [thread overview]
Message-ID: <20130521173332.637942da.akpm@linux-foundation.org> (raw)
In-Reply-To: <1368084089-24576-7-git-send-email-minchan@kernel.org>
On Thu, 9 May 2013 16:21:28 +0900 Minchan Kim <minchan@kernel.org> wrote:
> This patch adds address range reclaim of a process.
> The requirement is following as,
>
> Like webkit1, it uses a address space for handling multi tabs.
> IOW, it uses *one* process model so all tabs shares address space
> of the process. In such scenario, per-process reclaim is rather
> coarse-grained so this patch supports more fine-grained reclaim
> for being able to reclaim target address range of the process.
> For reclaim target range, you should use following format.
>
> echo [addr] [size-byte] > /proc/pid/reclaim
>
> The addr should be page-aligned.
>
> So now reclaim konb's interface is following as.
>
> echo file > /proc/pid/reclaim
> reclaim file-backed pages only
>
> echo anon > /proc/pid/reclaim
> reclaim anonymous pages only
>
> echo all > /proc/pid/reclaim
> reclaim all pages
>
> echo 0x100000 8K > /proc/pid/reclaim
> reclaim pages in (0x100000 - 0x102000)
This might be going a bit far. The application itself can be modified
to use fadvise/madvise/whatever to release unused pages and that's a
better interface.
Athough it's a bit of a pipe-dream, I do think we should encourage
userspace to go this path, rather than providing ways for hacky admin
tools to go poking around in /proc/pid/maps and whacking apps
externally.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-05-22 0:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 7:21 [PATCH v5 0/7] Per process reclaim Minchan Kim
2013-05-09 7:21 ` [PATCH v5 1/7] mm: prevent to write out dirty page in CMA by may_writepage Minchan Kim
2013-05-09 7:21 ` [PATCH v5 2/7] mm: Per process reclaim Minchan Kim
2013-05-09 7:21 ` [PATCH v5 3/7] mm: make shrink_page_list with pages work from multiple zones Minchan Kim
2013-05-09 7:21 ` [PATCH v5 4/7] mm: Remove shrink_page Minchan Kim
2013-05-09 7:21 ` [PATCH v5 5/7] mm: Enhance per process reclaim to consider shared pages Minchan Kim
2013-05-09 7:21 ` [PATCH v5 6/7] mm: Support address range reclaim Minchan Kim
2013-05-22 0:33 ` Andrew Morton [this message]
2013-05-27 8:24 ` Minchan Kim
2013-05-09 7:21 ` [PATCH v5 7/7] add documentation about reclaim knob on proc.txt Minchan Kim
2013-05-21 23:16 ` [PATCH v5 0/7] Per process reclaim Andrew Morton
2013-05-27 8:12 ` Minchan Kim
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=20130521173332.637942da.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=minkyung88@lge.com \
--cc=mtk.manpages@gmail.com \
--cc=namhyung@kernel.org \
--cc=riel@redhat.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).