From: "Zi Yan" <zi.yan@sent.com>
To: "Michal Hocko" <mhocko@kernel.org>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
"Naoya Horiguchi" <n-horiguchi@ah.jp.nec.com>,
linux-mm@kvack.org, "Andrew Morton" <akpm@linux-foundation.org>,
"Vlastimil Babka" <vbabka@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] mm: consider non-anonymous thp as unmovable page
Date: Thu, 05 Apr 2018 13:58:43 -0400 [thread overview]
Message-ID: <7C2DE363-E113-4284-B94F-814F386743DF@sent.com> (raw)
In-Reply-To: <20180405160317.GP6312@dhcp22.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]
On 5 Apr 2018, at 12:03, Michal Hocko wrote:
> On Thu 05-04-18 18:55:51, Kirill A. Shutemov wrote:
>> On Thu, Apr 05, 2018 at 05:05:47PM +0200, Michal Hocko wrote:
>>> On Thu 05-04-18 16:40:45, Kirill A. Shutemov wrote:
>>>> On Thu, Apr 05, 2018 at 02:48:30PM +0200, Michal Hocko wrote:
>>> [...]
>>>>> RIght, I confused the two. What is the proper layer to fix that then?
>>>>> rmap_walk_file?
>>>>
>>>> Maybe something like this? Totally untested.
>>>
>>> This looks way too complex. Why cannot we simply split THP page cache
>>> during migration?
>>
>> This way we unify the codepath for archictures that don't support THP
>> migration and shmem THP.
>
> But why? There shouldn't be really nothing to prevent THP (anon or
> shemem) to be migratable. If we cannot migrate it at once we can always
> split it. So why should we add another thp specific handling all over
> the place?
Then, it would be much easier if your "unclutter thp migration" patches is merged,
plus the patch below:
diff --git a/mm/migrate.c b/mm/migrate.c
index 60531108021a..b4087aa890f5 100644
--- a/mm/migrate.c
+++ b/mm/migrate.c
@@ -1138,7 +1138,9 @@ static ICE_noinline int unmap_and_move(new_page_t get_new_page,
int rc = MIGRATEPAGE_SUCCESS;
struct page *newpage;
- if (!thp_migration_supported() && PageTransHuge(page))
+ if ((!thp_migration_supported() ||
+ (thp_migration_supported() && !PageAnon(page))) &&
+ PageTransHuge(page))
return -ENOMEM;
newpage = get_new_page(page, private)
--
Best Regards
Yan Zi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 496 bytes --]
next prev parent reply other threads:[~2018-04-05 17:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 4:46 [PATCH v1] mm: consider non-anonymous thp as unmovable page Naoya Horiguchi
2018-04-03 7:59 ` Michal Hocko
2018-04-03 8:24 ` Naoya Horiguchi
2018-04-03 8:34 ` Michal Hocko
2018-04-03 10:54 ` Kirill A. Shutemov
2018-04-03 10:58 ` Michal Hocko
2018-04-03 11:16 ` Kirill A. Shutemov
2018-04-03 11:33 ` Michal Hocko
2018-04-05 8:59 ` Michal Hocko
2018-04-05 12:28 ` Kirill A. Shutemov
2018-04-05 12:48 ` Michal Hocko
2018-04-05 13:40 ` Kirill A. Shutemov
2018-04-05 15:05 ` Michal Hocko
2018-04-05 15:55 ` Kirill A. Shutemov
2018-04-05 16:03 ` Michal Hocko
2018-04-05 17:58 ` Zi Yan [this message]
2018-04-05 19:04 ` Michal Hocko
2018-04-05 19:09 ` Zi Yan
2018-04-06 3:07 ` [PATCH] mm: shmem: enable thp migration (Re: [PATCH v1] mm: consider non-anonymous thp as unmovable page) Naoya Horiguchi
2018-04-06 5:14 ` Naoya Horiguchi
2018-04-06 7:08 ` Michal Hocko
2018-04-09 7:14 ` Naoya Horiguchi
2018-04-10 11:16 ` Kirill A. Shutemov
2018-04-11 9:26 ` Michal Hocko
2018-04-11 19:27 ` Andrew Morton
2018-04-11 19:43 ` Michal Hocko
2018-04-23 3:03 ` Matthew Wilcox
2018-04-23 7:21 ` Naoya Horiguchi
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=7C2DE363-E113-4284-B94F-814F386743DF@sent.com \
--to=zi.yan@sent.com \
--cc=akpm@linux-foundation.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).