From: Kemeng Shi <shikemeng@huaweicloud.com>
To: Kairui Song <ryncsn@gmail.com>
Cc: akpm@linux-foundation.org, tim.c.chen@linux.intel.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/8] mm: swap: use swap_entries_free() to free swap entry in swap_entry_put_locked()
Date: Thu, 20 Mar 2025 09:05:45 +0800 [thread overview]
Message-ID: <cc20b08d-a43e-87ad-490d-12714602cd39@huaweicloud.com> (raw)
In-Reply-To: <CAMgjq7CXxpG0doC9iXAXkq_ozvN43gBbG7UsNk8_PYMvpLABHA@mail.gmail.com>
on 3/19/2025 2:08 AM, Kairui Song wrote:
> On Tue, Mar 18, 2025 at 2:10 PM Kemeng Shi <shikemeng@huaweicloud.com> wrote:
>>
>> In swap_entry_put_locked(), we will set slot to SWAP_HAS_CACHE before
>> using swap_entries_free() to do actual swap entry freeing. This
>> introduce an unnecessary intermediate state.
>> By using swap_entries_free() in swap_entry_put_locked(), we can
>> eliminate the need to set slot to SWAP_HAS_CACHE.
>> This change would make the behavior of swap_entry_put_locked() more
>> consistent with other put() operations which will do actual free work
>> after put last reference.
>>
>> Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com>
>> Reviewed-by: Tim Chen <tim.c.chen@linux.intel.com>
>> ---
>> mm/swapfile.c | 23 ++++++++++-------------
>> 1 file changed, 10 insertions(+), 13 deletions(-)
>>
>> diff --git a/mm/swapfile.c b/mm/swapfile.c
>> index 0aa7ce82c013..40e41e514813 100644
>> --- a/mm/swapfile.c
>> +++ b/mm/swapfile.c
>> @@ -1348,9 +1348,11 @@ static struct swap_info_struct *_swap_info_get(swp_entry_t entry)
>> }
>>
>> static unsigned char swap_entry_put_locked(struct swap_info_struct *si,
>> - unsigned long offset,
>> + struct swap_cluster_info *ci,
>> + swp_entry_t entry,
>> unsigned char usage)
>> {
>> + unsigned long offset = swp_offset(entry);
>> unsigned char count;
>> unsigned char has_cache;
>>
>> @@ -1382,7 +1384,7 @@ static unsigned char swap_entry_put_locked(struct swap_info_struct *si,
>> if (usage)
>> WRITE_ONCE(si->swap_map[offset], usage);
>> else
>> - WRITE_ONCE(si->swap_map[offset], SWAP_HAS_CACHE);
>> + swap_entries_free(si, ci, entry, 1);
>>
>> return usage;
>> }
>> @@ -1461,9 +1463,7 @@ static unsigned char swap_entry_put(struct swap_info_struct *si,
>> unsigned char usage;
>>
>> ci = lock_cluster(si, offset);
>> - usage = swap_entry_put_locked(si, offset, 1);
>> - if (!usage)
>> - swap_entries_free(si, ci, swp_entry(si->type, offset), 1);
>> + usage = swap_entry_put_locked(si, ci, entry, 1);
>> unlock_cluster(ci);
>>
>> return usage;
>> @@ -1551,8 +1551,8 @@ static void cluster_swap_free_nr(struct swap_info_struct *si,
>>
>> ci = lock_cluster(si, offset);
>> do {
>> - if (!swap_entry_put_locked(si, offset, usage))
>> - swap_entries_free(si, ci, swp_entry(si->type, offset), 1);
>> + swap_entry_put_locked(si, ci, swp_entry(si->type, offset),
>> + usage);
>> } while (++offset < end);
>> unlock_cluster(ci);
>> }
>> @@ -1596,12 +1596,9 @@ void put_swap_folio(struct folio *folio, swp_entry_t entry)
>> ci = lock_cluster(si, offset);
>> if (swap_only_has_cache(si, offset, size))
>> swap_entries_free(si, ci, entry, size);
>> - else {
>> - for (int i = 0; i < size; i++, entry.val++) {
>> - if (!swap_entry_put_locked(si, offset + i, SWAP_HAS_CACHE))
>> - swap_entries_free(si, ci, entry, 1);
>> - }
>> - }
>> + else
>> + for (int i = 0; i < size; i++, entry.val++)
>> + swap_entry_put_locked(si, ci, entry, SWAP_HAS_CACHE);
>
> I'd prefer you keep the bracket here for more readability, and maybe
> add bracket for the whole if statement, just a tiny nitpick so still:
Thanks for review. Both ways are acceptable to me. I will keep the
bracket in next version.
Thanks,
Kemeng
>
> Reviewed-by: Kairui Song <kasong@tencent.com>
>
>> unlock_cluster(ci);
>> }
>
>>
>> --
>> 2.30.0
>>
>
next prev parent reply other threads:[~2025-03-20 1:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 15:06 [PATCH v2 0/8] Minor cleanups and improvements to swap freeing code Kemeng Shi
2025-03-18 15:06 ` [PATCH v2 1/8] mm: swap: rename __swap_[entry/entries]_free[_locked] to swap_[entry/entries]_put[_locked] Kemeng Shi
2025-03-18 15:06 ` [PATCH v2 2/8] mm: swap: remove unneeded VM_BUG_ON(*map != SWAP_HAS_CACHE) in swap_entry_range_free() Kemeng Shi
2025-03-19 5:18 ` Kairui Song
2025-03-20 1:10 ` Kemeng Shi
2025-03-18 15:06 ` [PATCH v2 3/8] mm: swap: use swap_entries_free() to free swap entry in swap_entry_put_locked() Kemeng Shi
2025-03-18 18:08 ` Kairui Song
2025-03-20 1:05 ` Kemeng Shi [this message]
2025-03-18 15:06 ` [PATCH v2 4/8] mm: swap: use swap_entries_free() drop last ref count in swap_entries_put_nr() Kemeng Shi
2025-03-18 15:06 ` [PATCH v2 5/8] mm: swap: drop last SWAP_MAP_SHMEM flag in batch " Kemeng Shi
2025-03-18 15:06 ` [PATCH v2 6/8] mm: swap: free each cluster individually in swap_entries_put_map_nr() Kemeng Shi
2025-03-18 15:06 ` [PATCH v2 7/8] mm: swap: factor out helper to drop cache of entries within a single cluster Kemeng Shi
2025-03-18 15:06 ` [PATCH v2 8/8] mm: swap: replace cluster_swap_free_nr() with swap_entries_put_[map/cache]() Kemeng Shi
2025-03-18 17:03 ` [PATCH v2 0/8] Minor cleanups and improvements to swap freeing code Tim Chen
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=cc20b08d-a43e-87ad-490d-12714602cd39@huaweicloud.com \
--to=shikemeng@huaweicloud.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryncsn@gmail.com \
--cc=tim.c.chen@linux.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