From: Yin Fengwei <fengwei.yin@intel.com>
To: linux-mm@kvack.org, akpm@linux-foundation.org,
willy@infradead.org, yuzhao@google.com, ryan.roberts@arm.com
Cc: fengwei.yin@intel.com
Subject: [PATCH 1/2] THP: avoid lock when check whether THP is in deferred list
Date: Mon, 17 Apr 2023 15:56:42 +0800 [thread overview]
Message-ID: <20230417075643.3287513-2-fengwei.yin@intel.com> (raw)
In-Reply-To: <20230417075643.3287513-1-fengwei.yin@intel.com>
free_transhuge_page() acquires split queue lock then check
wether the THP was added to deferred list or not.
It's safe to check whether the THP is in deferred list or not.
When code hit free_transhuge_page(), there is no one tries
to update the folio's _deferred_list.
If folio is not in deferred_list, it's safe to check without
acquiring lock.
If folio is in deferred_list, the other node in deferred_list
adding/deleteing doesn't impact the return value of
list_epmty(@folio->_deferred_list).
Running page_fault1 of will-it-scale + order 2 folio for anonymous
mapping with 96 processes on an Ice Lake 48C/96T test box, we could
see the 61% split_queue_lock contention:
- 71.28% 0.35% page_fault1_pro [kernel.kallsyms] [k]
release_pages
- 70.93% release_pages
- 61.42% free_transhuge_page
+ 60.77% _raw_spin_lock_irqsave
With this patch applied, the split_queue_lock contention is less
than 1%.
Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
---
mm/huge_memory.c | 19 ++++++++++++++++---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index b0252b418ef01..802082531e606 100644
--- a/mm/huge_memory.c
+++ b/mm/huge_memory.c
@@ -2842,12 +2842,25 @@ void free_transhuge_page(struct page *page)
struct deferred_split *ds_queue = get_deferred_split_queue(folio);
unsigned long flags;
- spin_lock_irqsave(&ds_queue->split_queue_lock, flags);
- if (!list_empty(&folio->_deferred_list)) {
+ /*
+ * At this point, there is no one trying to queue the folio
+ * to deferred_list. folio->_deferred_list is not possible
+ * being updated.
+ *
+ * If folio is already added to deferred_list, add/delete to/from
+ * deferred_list will not impact list_empty(&folio->_deferred_list).
+ * It's safe to check list_empty(&folio->_deferred_list) without
+ * acquiring the lock.
+ *
+ * If folio is not in deferred_list, it's safe to check without
+ * acquiring the lock.
+ */
+ if (data_race(!list_empty(&folio->_deferred_list))) {
+ spin_lock_irqsave(&ds_queue->split_queue_lock, flags);
ds_queue->split_queue_len--;
list_del(&folio->_deferred_list);
+ spin_unlock_irqrestore(&ds_queue->split_queue_lock, flags);
}
- spin_unlock_irqrestore(&ds_queue->split_queue_lock, flags);
free_compound_page(page);
}
--
2.30.2
next prev parent reply other threads:[~2023-04-17 7:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 7:56 [PATCH 0/2] Reduce lock contention related with large folio Yin Fengwei
2023-04-17 7:56 ` Yin Fengwei [this message]
2023-04-17 7:56 ` [PATCH 2/2] lru: allow large batched add large folio to lru list Yin Fengwei
2023-04-17 12:25 ` Matthew Wilcox
2023-04-18 1:57 ` Yin Fengwei
2023-04-18 2:37 ` Yin Fengwei
2023-04-18 6:39 ` Huang, Ying
2023-04-17 10:33 ` [PATCH 0/2] Reduce lock contention related with large folio Ryan Roberts
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=20230417075643.3287513-2-fengwei.yin@intel.com \
--to=fengwei.yin@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=willy@infradead.org \
--cc=yuzhao@google.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