All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Minchan Kim <minchan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH 6/6] add documentation on proc.txt
Date: Mon, 22 Apr 2013 10:48:39 -0500	[thread overview]
Message-ID: <1366645719.18069.147@driftwood> (raw)
In-Reply-To: <1366620306-30940-6-git-send-email-minchan@kernel.org> (from minchan@kernel.org on Mon Apr 22 03:45:06 2013)

On 04/22/2013 03:45:06 AM, Minchan Kim wrote:
> This patch adds documentation about new reclaim field in proc.txt
> 
> Cc: Rob Landley <rob@landley.net>
> Signed-off-by: Minchan Kim <minchan@kernel.org>
> ---
>  Documentation/filesystems/proc.txt | 24 ++++++++++++++++++++++++
>  1 file changed, 24 insertions(+)
> 
> diff --git a/Documentation/filesystems/proc.txt  
> b/Documentation/filesystems/proc.txt
> index 488c094..c1f5ee4 100644
> --- a/Documentation/filesystems/proc.txt
> +++ b/Documentation/filesystems/proc.txt
> @@ -136,6 +136,7 @@ Table 1-1: Process specific entries in /proc
>   maps		Memory maps to executables and library files	 
> (2.4)
>   mem		Memory held by this process
>   root		Link to the root directory of this process
> + reclaim	Reclaim pages in this process
>   stat		Process status
>   statm		Process memory status information
>   status		Process status in human readable form
> @@ -489,6 +490,29 @@ To clear the soft-dirty bit
> 
>  Any other value written to /proc/PID/clear_refs will have no effect.
> 
> +The /proc/PID/reclaim is used to reclaim pages in this process.

Trivial nitpick: Either start with "The file" or just /proc/PID/reclaim

> +To reclaim file-backed pages,
> +    > echo 1 > /proc/PID/reclaim
> +
> +To reclaim anonymous pages,
> +    > echo 2 > /proc/PID/reclaim
> +
> +To reclaim both pages,
> +    > echo 3 > /proc/PID/reclaim
> +
> +Also, you can specify address range of process so part of address  
> space
> +will be reclaimed. The format is following as
> +    > echo 4 addr size > /proc/PID/reclaim

Size is in bytes or pages? (I'm guessing bytes. It must be a multiple  
of pages?)

So the following examples are telling it to reclaim a specific page?

> +To reclaim file-backed pages in address range,
> +    > echo 4 $((1<<20) 4096 > /proc/PID/reclaim
> +
> +To reclaim anonymous pages in address range,
> +    > echo 5 $((1<<20) 4096 > /proc/PID/reclaim
> +
> +To reclaim both pages in address range,
> +    > echo 6 $((1<<20) 4096 > /proc/PID/reclaim
> +
>  The /proc/pid/pagemap gives the PFN, which can be used to find the  
> pageflags
>  using /proc/kpageflags and number of times a page is mapped using
>  /proc/kpagecount. For detailed explanation, see  
> Documentation/vm/pagemap.txt.

Otherwise, if the series goes in I'm fine with this going in with it.

Acked-by: Rob Landley <rob@landley.net>

Rob
--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Rob Landley <rob@landley.net>
To: Minchan Kim <minchan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	Rik van Riel <riel@redhat.com>, Minchan Kim <minchan@kernel.org>
Subject: Re: [PATCH 6/6] add documentation on proc.txt
Date: Mon, 22 Apr 2013 10:48:39 -0500	[thread overview]
Message-ID: <1366645719.18069.147@driftwood> (raw)
In-Reply-To: <1366620306-30940-6-git-send-email-minchan@kernel.org> (from minchan@kernel.org on Mon Apr 22 03:45:06 2013)

On 04/22/2013 03:45:06 AM, Minchan Kim wrote:
> This patch adds documentation about new reclaim field in proc.txt
> 
> Cc: Rob Landley <rob@landley.net>
> Signed-off-by: Minchan Kim <minchan@kernel.org>
> ---
>  Documentation/filesystems/proc.txt | 24 ++++++++++++++++++++++++
>  1 file changed, 24 insertions(+)
> 
> diff --git a/Documentation/filesystems/proc.txt  
> b/Documentation/filesystems/proc.txt
> index 488c094..c1f5ee4 100644
> --- a/Documentation/filesystems/proc.txt
> +++ b/Documentation/filesystems/proc.txt
> @@ -136,6 +136,7 @@ Table 1-1: Process specific entries in /proc
>   maps		Memory maps to executables and library files	 
> (2.4)
>   mem		Memory held by this process
>   root		Link to the root directory of this process
> + reclaim	Reclaim pages in this process
>   stat		Process status
>   statm		Process memory status information
>   status		Process status in human readable form
> @@ -489,6 +490,29 @@ To clear the soft-dirty bit
> 
>  Any other value written to /proc/PID/clear_refs will have no effect.
> 
> +The /proc/PID/reclaim is used to reclaim pages in this process.

Trivial nitpick: Either start with "The file" or just /proc/PID/reclaim

> +To reclaim file-backed pages,
> +    > echo 1 > /proc/PID/reclaim
> +
> +To reclaim anonymous pages,
> +    > echo 2 > /proc/PID/reclaim
> +
> +To reclaim both pages,
> +    > echo 3 > /proc/PID/reclaim
> +
> +Also, you can specify address range of process so part of address  
> space
> +will be reclaimed. The format is following as
> +    > echo 4 addr size > /proc/PID/reclaim

Size is in bytes or pages? (I'm guessing bytes. It must be a multiple  
of pages?)

So the following examples are telling it to reclaim a specific page?

> +To reclaim file-backed pages in address range,
> +    > echo 4 $((1<<20) 4096 > /proc/PID/reclaim
> +
> +To reclaim anonymous pages in address range,
> +    > echo 5 $((1<<20) 4096 > /proc/PID/reclaim
> +
> +To reclaim both pages in address range,
> +    > echo 6 $((1<<20) 4096 > /proc/PID/reclaim
> +
>  The /proc/pid/pagemap gives the PFN, which can be used to find the  
> pageflags
>  using /proc/kpageflags and number of times a page is mapped using
>  /proc/kpagecount. For detailed explanation, see  
> Documentation/vm/pagemap.txt.

Otherwise, if the series goes in I'm fine with this going in with it.

Acked-by: Rob Landley <rob@landley.net>

Rob

  reply	other threads:[~2013-04-22 15:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22  8:45 [PATCH 1/6] mm: Per process reclaim Minchan Kim
2013-04-22  8:45 ` Minchan Kim
2013-04-22  8:45 ` [PATCH 2/6] mm: make shrink_page_list with pages work from multiple zones Minchan Kim
2013-04-22  8:45   ` Minchan Kim
2013-04-22  8:45 ` [PATCH 3/6] mm: Remove shrink_page Minchan Kim
2013-04-22  8:45   ` Minchan Kim
2013-04-22  8:45 ` [PATCH 4/6] mm: Enhance per process reclaim to consider shared pages Minchan Kim
2013-04-22  8:45   ` Minchan Kim
2013-04-22  8:45 ` [PATCH 5/6] mm: Support address range reclaim Minchan Kim
2013-04-22  8:45   ` Minchan Kim
2013-04-22  8:45 ` [PATCH 6/6] add documentation on proc.txt Minchan Kim
2013-04-22  8:45   ` Minchan Kim
2013-04-22 15:48   ` Rob Landley [this message]
2013-04-22 15:48     ` Rob Landley
2013-04-23  1:26     ` Minchan Kim
2013-04-23  1:26       ` Minchan Kim
2013-04-22 16:17   ` Dave Hansen
2013-04-22 16:17     ` Dave Hansen
2013-04-23  1:53     ` Minchan Kim
2013-04-23  1:53       ` Minchan Kim
2013-04-23 14:33       ` Dave Hansen
2013-04-23 14:33         ` Dave Hansen
2013-04-24  1:42         ` Minchan Kim
2013-04-24  1:42           ` 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=1366645719.18069.147@driftwood \
    --to=rob@landley.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=mtk.manpages@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.