From: Liu ping fan <kernelfans@gmail.com>
To: Hugh Dickins <hughd@google.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm: swap: avoid to writepage when a page is !PageSwapCache
Date: Wed, 2 Jul 2014 14:50:12 +0800 [thread overview]
Message-ID: <CAFgQCTuUPm0EbOYsJOMdM5MV2qqGuCbcSSB30UvwK6=6kbCUgg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1407012101160.1009@eggly.anvils>
On Wed, Jul 2, 2014 at 12:29 PM, Hugh Dickins <hughd@google.com> wrote:
> On Wed, 2 Jul 2014, Liu Ping Fan wrote:
>
>> There is race between do_swap_page() and swap_writepage(), if
>> do_swap_page() had deleted a page from swap cache, there is no need
>> to write it. So changing the ret of try_to_free_swap() to make
>> swap_writepage() aware of this scene.
>
> Is this an inefficiency that you have noticed in practice,
> or something that you think you spotted by code inspection?
>
just spotted by code inspection.
> I don't see how it can happen: all the places I know of that call
> swap_writepage() (including vmscan.c's mapping->a_ops->writepage)
> have not dropped page lock since setting or checking PageSwapCache,
> and page lock is supposed to protect against deletion from swap cache.
>
> Has that changed? Please point out where.
>
No, my fault. Thanks for making me aware of this.
>>
>> Signed-off-by: Liu Ping Fan <pingfank@linux.vnet.ibm.com>
>> ---
>> mm/swapfile.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/mm/swapfile.c b/mm/swapfile.c
>> index 4c524f7..9d80671 100644
>> --- a/mm/swapfile.c
>> +++ b/mm/swapfile.c
>> @@ -910,7 +910,7 @@ int try_to_free_swap(struct page *page)
>> VM_BUG_ON_PAGE(!PageLocked(page), page);
>>
>> if (!PageSwapCache(page))
>> - return 0;
>> + return -1;
>
> Previously it returned either 0 or 1, which is what __try_to_reclaim_swap()
> says it returns; so better to stick to 0 or 1, unless you have good reason
> to add a distinct value.
>
> It's true that by the time __try_to_reclaim_swap() has got the page lock,
> the page might have been removed from swap cache, and we could then treat
> that as swap_was_freed (even though it was not freed by the caller).
>
> But it's a very narrow window, and no great advantage to do so:
> I don't think it's worth changing try_to_free_swap() semantics for,
> but you could persuade us.
>
Got it, and it is meaningless to do that.
Thanks,
Fan
--
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-07-02 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 3:42 [PATCH] mm: swap: avoid to writepage when a page is !PageSwapCache Liu Ping Fan
2014-07-02 4:29 ` Hugh Dickins
2014-07-02 6:50 ` Liu ping fan [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='CAFgQCTuUPm0EbOYsJOMdM5MV2qqGuCbcSSB30UvwK6=6kbCUgg@mail.gmail.com' \
--to=kernelfans@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
/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).