From: Michal Hocko <mhocko@kernel.org>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Minchan Kim <minchan@kernel.org>, Hugh Dickins <hughd@google.com>,
Rik van Riel <riel@surriel.com>
Subject: Re: [PATCH] mm, trivial: Simplify swap related code in try_to_unmap_one()
Date: Tue, 31 Mar 2020 11:41:08 +0200 [thread overview]
Message-ID: <20200331094108.GF30449@dhcp22.suse.cz> (raw)
In-Reply-To: <20200331084613.1258555-1-ying.huang@intel.com>
On Tue 31-03-20 16:46:13, Huang, Ying wrote:
> From: Huang Ying <ying.huang@intel.com>
>
> Because PageSwapCache() will always return false if PageSwapBacked() returns
> false, and PageSwapBacked() will be check for MADV_FREE pages in
> try_to_unmap_one(). The swap related code in try_to_unmap_one() can be
> simplified to improve the readability.
My understanding is that this is a sanity check to let us know if
something breaks. Do we really want to get rid of it? Maybe it is not
really useful but if that is the case then the changelog should reflect
this fact.
> Signed-off-by: "Huang, Ying" <ying.huang@intel.com>
> Cc: Michal Hocko <mhocko@kernel.org>
> Cc: Minchan Kim <minchan@kernel.org>
> Cc: Hugh Dickins <hughd@google.com>
> Cc: Rik van Riel <riel@surriel.com>
> ---
> mm/rmap.c | 27 ++++++++++++++-------------
> 1 file changed, 14 insertions(+), 13 deletions(-)
>
> diff --git a/mm/rmap.c b/mm/rmap.c
> index 2126fd4a254b..cd3c406aeac7 100644
> --- a/mm/rmap.c
> +++ b/mm/rmap.c
> @@ -1613,19 +1613,6 @@ static bool try_to_unmap_one(struct page *page, struct vm_area_struct *vma,
> } else if (PageAnon(page)) {
> swp_entry_t entry = { .val = page_private(subpage) };
> pte_t swp_pte;
> - /*
> - * Store the swap location in the pte.
> - * See handle_pte_fault() ...
> - */
> - if (unlikely(PageSwapBacked(page) != PageSwapCache(page))) {
> - WARN_ON_ONCE(1);
> - ret = false;
> - /* We have to invalidate as we cleared the pte */
> - mmu_notifier_invalidate_range(mm, address,
> - address + PAGE_SIZE);
> - page_vma_mapped_walk_done(&pvmw);
> - break;
> - }
>
> /* MADV_FREE page check */
> if (!PageSwapBacked(page)) {
> @@ -1648,6 +1635,20 @@ static bool try_to_unmap_one(struct page *page, struct vm_area_struct *vma,
> break;
> }
>
> + /*
> + * Store the swap location in the pte.
> + * See handle_pte_fault() ...
> + */
> + if (unlikely(!PageSwapCache(page))) {
> + WARN_ON_ONCE(1);
> + ret = false;
> + /* We have to invalidate as we cleared the pte */
> + mmu_notifier_invalidate_range(mm, address,
> + address + PAGE_SIZE);
> + page_vma_mapped_walk_done(&pvmw);
> + break;
> + }
> +
> if (swap_duplicate(entry) < 0) {
> set_pte_at(mm, address, pvmw.pte, pteval);
> ret = false;
> --
> 2.25.0
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2020-03-31 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 8:46 Huang, Ying
2020-03-31 9:41 ` Michal Hocko [this message]
2020-04-01 1:11 ` Huang, Ying
2020-04-01 8:31 ` Michal Hocko
2020-04-01 8:48 ` Huang, Ying
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=20200331094108.GF30449@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=riel@surriel.com \
--cc=ying.huang@intel.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