From: Hugh Dickins <hughd@google.com>
To: Jamie Liu <jamieliu@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Shaohua Li <shli@fusionio.com>, Minchan Kim <minchan@kernel.org>,
Akinobu Mita <akinobu.mita@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] swap: do not skip lowest_bit in scan_swap_map() scan loop
Date: Tue, 21 Jan 2014 23:00:44 -0800 (PST) [thread overview]
Message-ID: <alpine.LSU.2.11.1401212251310.1001@eggly.anvils> (raw)
In-Reply-To: <1390357276-16521-1-git-send-email-jamieliu@google.com>
On Tue, 21 Jan 2014, Jamie Liu wrote:
> In the second half of scan_swap_map()'s scan loop, offset is set to
> si->lowest_bit and then incremented before entering the loop for the
> first time, causing si->swap_map[si->lowest_bit] to be skipped.
>
> Signed-off-by: Jamie Liu <jamieliu@google.com>
Acked-by: Hugh Dickins <hughd@google.com>
Good catch. At first I was puzzled that this off-by-one could have
gone unnoticed for so long (ever since 2.6.29); but now I think that
almost always we have a good amount of slack, in those pages duplicated
between swap and swapcache, which can be reclaimed at the vm_swap_full()
check, and so conceal this loss of a single slot.
> ---
> mm/swapfile.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/mm/swapfile.c b/mm/swapfile.c
> index 612a7c9..6635081 100644
> --- a/mm/swapfile.c
> +++ b/mm/swapfile.c
> @@ -616,7 +616,7 @@ scan:
> }
> }
> offset = si->lowest_bit;
> - while (++offset < scan_base) {
> + while (offset < scan_base) {
> if (!si->swap_map[offset]) {
> spin_lock(&si->lock);
> goto checks;
> @@ -629,6 +629,7 @@ scan:
> cond_resched();
> latency_ration = LATENCY_LIMIT;
> }
> + offset++;
> }
> spin_lock(&si->lock);
>
> --
> 1.8.5.3
>
>
--
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>
prev parent reply other threads:[~2014-01-22 7:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 2:21 Jamie Liu
2014-01-22 7:00 ` Hugh Dickins [this message]
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=alpine.LSU.2.11.1401212251310.1001@eggly.anvils \
--to=hughd@google.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jamieliu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=shli@fusionio.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