From: Minchan Kim <minchan@kernel.org>
To: ehrhardt@linux.vnet.ibm.com
Cc: linux-mm@kvack.org, axboe@kernel.dk,
Rik van Riel <riel@redhat.com>, Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] documentation: update how page-cluster affects swap I/O
Date: Tue, 15 May 2012 13:48:15 +0900 [thread overview]
Message-ID: <4FB1E00F.2000903@kernel.org> (raw)
In-Reply-To: <1336996709-8304-3-git-send-email-ehrhardt@linux.vnet.ibm.com>
On 05/14/2012 08:58 PM, ehrhardt@linux.vnet.ibm.com wrote:
> From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
>
> Fix of the documentation of /proc/sys/vm/page-cluster to match the behavior of
> the code and add some comments about what the tunable will change in that
> behavior.
>
> Signed-off-by: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
> ---
> Documentation/sysctl/vm.txt | 12 ++++++++++--
> 1 files changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/sysctl/vm.txt b/Documentation/sysctl/vm.txt
> index 96f0ee8..4d87dc0 100644
> --- a/Documentation/sysctl/vm.txt
> +++ b/Documentation/sysctl/vm.txt
> @@ -574,16 +574,24 @@ of physical RAM. See above.
>
> page-cluster
>
> -page-cluster controls the number of pages which are written to swap in
> -a single attempt. The swap I/O size.
> +page-cluster controls the number of pages up to which consecutive pages (if
> +available) are read in from swap in a single attempt. This is the swap
"If available" would be wrong in next kernel because recently Rik submit following patch,
mm: make swapin readahead skip over holes
http://marc.info/?l=linux-mm&m=132743264912987&w=4
> +counterpart to page cache readahead.
> +The mentioned consecutivity is not in terms of virtual/physical addresses,
> +but consecutive on swap space - that means they were swapped out together.
>
> It is a logarithmic value - setting it to zero means "1 page", setting
> it to 1 means "2 pages", setting it to 2 means "4 pages", etc.
> +Zero disables swap readahead completely.
>
> The default value is three (eight pages at a time). There may be some
> small benefits in tuning this to a different value if your workload is
> swap-intensive.
>
> +Lower values mean lower latencies for initial faults, but at the same time
> +extra faults and I/O delays for following faults if they would have been part of
> +that consecutive pages readahead would have brought in.
> +
> =============================================================
>
> panic_on_oom
Otherwise, Looks good to me.
--
Kind regards,
Minchan Kim
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-05-15 4:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 11:58 [PATCH 0/2] swap: improve swap I/O rate ehrhardt
2012-05-14 11:58 ` [PATCH 1/2] swap: allow swap readahead to be merged ehrhardt
2012-05-15 4:38 ` Minchan Kim
2012-05-15 17:43 ` Rik van Riel
2012-05-14 11:58 ` [PATCH 2/2] documentation: update how page-cluster affects swap I/O ehrhardt
2012-05-15 4:48 ` Minchan Kim [this message]
2012-05-21 7:24 ` Christian Ehrhardt
2012-05-15 4:59 ` [PATCH 0/2] swap: improve swap I/O rate Minchan Kim
2012-05-21 7:51 ` Christian Ehrhardt
2012-05-21 8:46 ` Minchan Kim
2012-05-15 18:24 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2012-05-21 8:09 [PATCH 0/2] swap: improve swap I/O rate - V2 ehrhardt
2012-05-21 8:09 ` [PATCH 2/2] documentation: update how page-cluster affects swap I/O ehrhardt
2012-05-21 8:48 ` Minchan Kim
2012-06-04 8:33 [PATCH 0/2] swap: improve swap I/O rate - V2 ehrhardt
2012-06-04 8:33 ` [PATCH 2/2] documentation: update how page-cluster affects swap I/O ehrhardt
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=4FB1E00F.2000903@kernel.org \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=ehrhardt@linux.vnet.ibm.com \
--cc=hughd@google.com \
--cc=linux-mm@kvack.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).