From: "Huang\, Ying" <ying.huang@intel.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: <akpm@linux-foundation.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <tim.c.chen@linux.intel.com>
Subject: Re: [PATCH 4/4] mm/swapfile.c: move new_cluster to check free_clusters directly
Date: Mon, 20 Apr 2020 09:41:43 +0800 [thread overview]
Message-ID: <87blnnszl4.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20200419013921.14390-4-richard.weiyang@gmail.com> (Wei Yang's message of "Sun, 19 Apr 2020 01:39:21 +0000")
Wei Yang <richard.weiyang@gmail.com> writes:
> Each time it needs jump to new_cluster, it is sure current
> percpu_cluster is null.
>
> Move the new_cluster to check free_clusters directly.
>
> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
> ---
> mm/swapfile.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/swapfile.c b/mm/swapfile.c
> index 07b0bc095411..78e92ff14c79 100644
> --- a/mm/swapfile.c
> +++ b/mm/swapfile.c
> @@ -603,9 +603,9 @@ static bool scan_swap_map_try_ssd_cluster(struct swap_info_struct *si,
> struct swap_cluster_info *ci;
> unsigned long tmp, max;
>
> -new_cluster:
> cluster = this_cpu_ptr(si->percpu_cluster);
> if (cluster_is_null(&cluster->index)) {
> +new_cluster:
> if (!cluster_list_empty(&si->free_clusters)) {
> cluster->index = si->free_clusters.head;
> cluster->next = cluster_next(&cluster->index) *
In swap_do_scheduled_discard(), we will unlock si->lock, so the
percpu_cluster may be changed after we releasing the lock. Or the
current thread may be moved to a different CPU.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2020-04-20 1:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 1:39 [PATCH 1/4] mm/swapfile.c: found_free could be represented by (tmp < max) Wei Yang
2020-04-19 1:39 ` [PATCH 2/4] mm/swapfile.c: tmp is always smaller than max Wei Yang
2020-04-19 1:39 ` [PATCH 4/4] mm/swapfile.c: move new_cluster to check free_clusters directly Wei Yang
2020-04-20 1:41 ` Huang, Ying [this message]
2020-04-20 21:45 ` Wei Yang
[not found] ` <20200419013921.14390-3-richard.weiyang@gmail.com>
2020-04-20 1:03 ` [PATCH 3/4] mm/swapfile.c: compare tmp and max after trying to iterate on swap_map Huang, Ying
2020-04-20 21:37 ` Wei Yang
2020-04-20 23:51 ` 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=87blnnszl4.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richard.weiyang@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