From: "Huang, Ying" <ying.huang@intel.com>
To: Kairui Song <ryncsn@gmail.com>
Cc: linux-mm@kvack.org, Kairui Song <kasong@tencent.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Miaohe Lin <linmiaohe@huawei.com>,
David Hildenbrand <david@redhat.com>,
Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH 1/5] swapfile: get rid of volatile and avoid redundant read
Date: Fri, 09 Dec 2022 10:48:41 +0800 [thread overview]
Message-ID: <874ju5s35i.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <20221208180209.50845-2-ryncsn@gmail.com> (Kairui Song's message of "Fri, 9 Dec 2022 02:02:05 +0800")
Kairui Song <ryncsn@gmail.com> writes:
> From: Kairui Song <kasong@tencent.com>
>
> Convert a volatile variable to more readable READ_ONCE. And this
> actually avoids the code from reading the variable twice redundantly
> when it races.
>
> Signed-off-by: Kairui Song <kasong@tencent.com>
LGTM, Thanks!
Reviewed-by: "Huang, Ying" <ying.huang@intel.com>
> ---
> mm/swapfile.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/mm/swapfile.c b/mm/swapfile.c
> index 72e481aacd5d..ff4f3cb85232 100644
> --- a/mm/swapfile.c
> +++ b/mm/swapfile.c
> @@ -1836,13 +1836,13 @@ static int unuse_pte_range(struct vm_area_struct *vma, pmd_t *pmd,
> pte_t *pte;
> struct swap_info_struct *si;
> int ret = 0;
> - volatile unsigned char *swap_map;
>
> si = swap_info[type];
> pte = pte_offset_map(pmd, addr);
> do {
> struct folio *folio;
> unsigned long offset;
> + unsigned char swp_count;
>
> if (!is_swap_pte(*pte))
> continue;
> @@ -1853,7 +1853,6 @@ static int unuse_pte_range(struct vm_area_struct *vma, pmd_t *pmd,
>
> offset = swp_offset(entry);
> pte_unmap(pte);
> - swap_map = &si->swap_map[offset];
> folio = swap_cache_get_folio(entry, vma, addr);
> if (!folio) {
> struct page *page;
> @@ -1870,8 +1869,10 @@ static int unuse_pte_range(struct vm_area_struct *vma, pmd_t *pmd,
> folio = page_folio(page);
> }
> if (!folio) {
> - if (*swap_map == 0 || *swap_map == SWAP_MAP_BAD)
> + swp_count = READ_ONCE(si->swap_map[offset]);
> + if (swp_count == 0 || swp_count == SWAP_MAP_BAD)
> goto try_next;
> +
> return -ENOMEM;
> }
next prev parent reply other threads:[~2022-12-09 2:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 18:02 [PATCH 0/5] Clean up and fixes for swap Kairui Song
2022-12-08 18:02 ` [PATCH 1/5] swapfile: get rid of volatile and avoid redundant read Kairui Song
2022-12-09 2:48 ` Huang, Ying [this message]
2022-12-08 18:02 ` [PATCH 2/5] swap: avoid a redundant pte map if ra window is 1 Kairui Song
2022-12-09 3:15 ` Huang, Ying
2022-12-08 18:02 ` [PATCH 3/5] swap: fold swap_ra_clamp_pfn into swap_ra_info Kairui Song
2022-12-08 19:08 ` Matthew Wilcox
2022-12-09 2:00 ` Kairui Song
2022-12-09 3:23 ` Huang, Ying
2022-12-08 18:02 ` [PATCH 4/5] swap: remove the swap lock in swap_cache_get_folio Kairui Song
2022-12-11 11:39 ` Huang, Ying
2022-12-11 11:47 ` Kairui Song
2022-12-08 18:02 ` [PATCH 5/5] swap: avoid ra statistic lost when swapin races Kairui Song
2022-12-08 19:14 ` Matthew Wilcox
2022-12-09 1:54 ` Kairui Song
2022-12-11 12:02 ` Huang, Ying
2022-12-11 12:15 ` Kairui Song
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=874ju5s35i.fsf@yhuang6-desk2.ccr.corp.intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=kasong@tencent.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryncsn@gmail.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