From: Alex Shi <alex.shi@linux.alibaba.com>
To: Johannes Weiner <hannes@cmpxchg.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Matthew Wilcox <willy@infradead.org>,
Linux-MM <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Hugh Dickins <hughd@google.com>
Subject: a question of split_huge_page
Date: Thu, 9 Jul 2020 23:11:11 +0800 [thread overview]
Message-ID: <df2597f6-af21-5547-d39c-94c02ad17adb@linux.alibaba.com> (raw)
Hi Kirill & Matthew,
In the func call chain, from split_huge_page() to lru_add_page_tail(),
Seems tail pages are added to lru list at line 963, but in this scenario
the head page has no lru bit and isn't set the bit later. Why we do this?
or do I miss sth?
Many Thanks
Alex
938 void lru_add_page_tail(struct page *page, struct page *page_tail,
939 struct lruvec *lruvec, struct list_head *list)
940 {
941 VM_BUG_ON_PAGE(!PageHead(page), page);
942 VM_BUG_ON_PAGE(PageCompound(page_tail), page);
943 VM_BUG_ON_PAGE(PageLRU(page_tail), page);
944 lockdep_assert_held(&lruvec_pgdat(lruvec)->lru_lock);
945
946 if (!list)
947 SetPageLRU(page_tail);
948
949 if (likely(PageLRU(page)))
950 list_add_tail(&page_tail->lru, &page->lru);
951 else if (list) {
952 /* page reclaim is reclaiming a huge page */
953 get_page(page_tail);
954 list_add_tail(&page_tail->lru, list);
955 } else {
956 /*
957 * Head page has not yet been counted, as an hpage,
958 * so we must account for each subpage individually.
959 *
960 * Put page_tail on the list at the correct position
961 * so they all end up in order.
962 */
963 add_page_to_lru_list_tail(page_tail, lruvec,
964 page_lru(page_tail));
965 }
966 }
next reply other threads:[~2020-07-09 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 15:11 Alex Shi [this message]
2020-07-09 15:50 ` Matthew Wilcox
2020-07-09 16:07 ` Kirill A. Shutemov
2020-07-10 4:51 ` Alex Shi
2020-07-10 5:28 ` Mika Penttilä
2020-07-10 7:00 ` Alex Shi
2020-07-10 7:22 ` Mika Penttilä
2020-07-10 9:34 ` Alex Shi
2020-07-10 12:56 ` Joerg Roedel
2020-07-10 17:29 ` Yang Shi
2020-07-10 10:33 ` Kirill A. Shutemov
2020-07-10 14:23 ` Alex Shi
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=df2597f6-af21-5547-d39c-94c02ad17adb@linux.alibaba.com \
--to=alex.shi@linux.alibaba.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.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