From: Andrew Morton <akpm@linux-foundation.org>
To: Jiexun Wang <wangjiexun@tinylab.org>
Cc: brauner@kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, falcon@tinylab.org
Subject: Re: [PATCH 1/1] mm/madvise: add cond_resched() in madvise_cold_or_pageout_pte_range()
Date: Sun, 10 Sep 2023 12:33:35 -0700 [thread overview]
Message-ID: <20230910123335.36ebf58e46628eeffef612c3@linux-foundation.org> (raw)
In-Reply-To: <95d610623363009a71024c7a473d6895f39f3caf.1694219361.git.wangjiexun@tinylab.org>
On Sat, 9 Sep 2023 13:33:08 +0800 Jiexun Wang <wangjiexun@tinylab.org> wrote:
> Currently the madvise_cold_or_pageout_pte_range() function exhibits
> significant latency under memory pressure, which can be effectively
> reduced by adding cond_resched() within the loop.
>
> When the batch_count reaches SWAP_CLUSTER_MAX, we reschedule
> the task to ensure fairness and avoid long lock holding times.
>
> ...
>
> @@ -441,6 +443,13 @@ static int madvise_cold_or_pageout_pte_range(pmd_t *pmd,
> arch_enter_lazy_mmu_mode();
> for (; addr < end; pte++, addr += PAGE_SIZE) {
> ptent = ptep_get(pte);
> +
> + if (++batch_count == SWAP_CLUSTER_MAX) {
> + pte_unmap_unlock(start_pte, ptl);
> + cond_resched();
> + start_pte = pte_offset_map_lock(mm, pmd, addr, &ptl);
> + batch_count = 0;
> + }
>
> if (pte_none(ptent))
> continue;
I doubt if we can simply drop the lock like this then proceed as if
nothing has changed while the lock was released.
Could be that something along these lines:
@@ -434,6 +436,7 @@ huge_unlock:
regular_folio:
#endif
tlb_change_page_size(tlb, PAGE_SIZE);
+restart:
start_pte = pte = pte_offset_map_lock(vma->vm_mm, pmd, addr, &ptl);
if (!start_pte)
return 0;
@@ -441,6 +444,15 @@ regular_folio:
arch_enter_lazy_mmu_mode();
for (; addr < end; pte++, addr += PAGE_SIZE) {
ptent = ptep_get(pte);
+
+ if (++batch_count == SWAP_CLUSTER_MAX) {
+ batch_count = 0;
+ if (need_resched()) {
+ pte_unmap_unlock(start_pte, ptl);
+ cond_resched();
+ goto restart;
+ }
+ }
if (pte_none(ptent))
continue;
would work, but more analysis would be needed.
next prev parent reply other threads:[~2023-09-10 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 5:33 [PATCH 0/1] " Jiexun Wang
2023-09-09 5:33 ` [PATCH 1/1] " Jiexun Wang
2023-09-10 19:33 ` Andrew Morton [this message]
2023-09-12 17:58 ` kernel test robot
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=20230910123335.36ebf58e46628eeffef612c3@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wangjiexun@tinylab.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