From: Zi Yan <ziy@nvidia.com> To: Roman Gushchin <roman.gushchin@linux.dev> Cc: Matthew Wilcox <willy@infradead.org>, linux-mm@kvack.org, Shuah Khan <shuah@kernel.org>, Yang Shi <shy828301@gmail.com>, Miaohe Lin <linmiaohe@huawei.com>, Hugh Dickins <hughd@google.com>, "Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>, linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, linux-kselftest@vger.kernel.org Subject: Re: [RFC PATCH 1/5] mm: memcg: make memcg huge page split support any order split. Date: Mon, 21 Mar 2022 15:07:46 -0400 [thread overview] Message-ID: <0001CABA-9436-4EFF-9C7F-F67300D09DA1@nvidia.com> (raw) In-Reply-To: <YjjKh2NoWGcq28Oo@carbon.dhcp.thefacebook.com> [-- Attachment #1: Type: text/plain, Size: 1378 bytes --] On 21 Mar 2022, at 14:57, Roman Gushchin wrote: > On Mon, Mar 21, 2022 at 10:21:24AM -0400, Zi Yan wrote: >> From: Zi Yan <ziy@nvidia.com> >> >> It sets memcg information for the pages after the split. A new parameter >> new_order is added to tell the new page order, always 0 for now. It >> prepares for upcoming changes to support split huge page to any lower >> order. >> >> Signed-off-by: Zi Yan <ziy@nvidia.com> >> --- >> include/linux/memcontrol.h | 2 +- >> mm/huge_memory.c | 2 +- >> mm/memcontrol.c | 10 +++++----- >> mm/page_alloc.c | 2 +- >> 4 files changed, 8 insertions(+), 8 deletions(-) >> >> diff --git a/include/linux/memcontrol.h b/include/linux/memcontrol.h >> index 89b14729d59f..e71189454bf0 100644 >> --- a/include/linux/memcontrol.h >> +++ b/include/linux/memcontrol.h >> @@ -1116,7 +1116,7 @@ static inline void memcg_memory_event_mm(struct mm_struct *mm, >> rcu_read_unlock(); >> } >> >> -void split_page_memcg(struct page *head, unsigned int nr); >> +void split_page_memcg(struct page *head, unsigned int nr, unsigned int new_order); > > It looks a bit inconsistent, can't we switch to use either nr or order for both > arguments? The latter is preferable. Yes. Will change it to new_nr to be consistent. > > Other than that, the patch looks good to me. Thank you for the review. -- Best Regards, Yan, Zi [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 854 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Zi Yan <ziy-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> To: Roman Gushchin <roman.gushchin-fxUVXftIFDnyG1zEObXtfA@public.gmane.org> Cc: Matthew Wilcox <willy-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>, linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org, Shuah Khan <shuah-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>, Yang Shi <shy828301-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>, Miaohe Lin <linmiaohe-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>, Hugh Dickins <hughd-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>, "Kirill A . Shutemov" <kirill.shutemov-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kselftest-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Subject: Re: [RFC PATCH 1/5] mm: memcg: make memcg huge page split support any order split. Date: Mon, 21 Mar 2022 15:07:46 -0400 [thread overview] Message-ID: <0001CABA-9436-4EFF-9C7F-F67300D09DA1@nvidia.com> (raw) In-Reply-To: <YjjKh2NoWGcq28Oo-cx5fftMpWqeCjSd+JxjunQ2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org> [-- Attachment #1: Type: text/plain, Size: 1409 bytes --] On 21 Mar 2022, at 14:57, Roman Gushchin wrote: > On Mon, Mar 21, 2022 at 10:21:24AM -0400, Zi Yan wrote: >> From: Zi Yan <ziy-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> >> >> It sets memcg information for the pages after the split. A new parameter >> new_order is added to tell the new page order, always 0 for now. It >> prepares for upcoming changes to support split huge page to any lower >> order. >> >> Signed-off-by: Zi Yan <ziy-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> >> --- >> include/linux/memcontrol.h | 2 +- >> mm/huge_memory.c | 2 +- >> mm/memcontrol.c | 10 +++++----- >> mm/page_alloc.c | 2 +- >> 4 files changed, 8 insertions(+), 8 deletions(-) >> >> diff --git a/include/linux/memcontrol.h b/include/linux/memcontrol.h >> index 89b14729d59f..e71189454bf0 100644 >> --- a/include/linux/memcontrol.h >> +++ b/include/linux/memcontrol.h >> @@ -1116,7 +1116,7 @@ static inline void memcg_memory_event_mm(struct mm_struct *mm, >> rcu_read_unlock(); >> } >> >> -void split_page_memcg(struct page *head, unsigned int nr); >> +void split_page_memcg(struct page *head, unsigned int nr, unsigned int new_order); > > It looks a bit inconsistent, can't we switch to use either nr or order for both > arguments? The latter is preferable. Yes. Will change it to new_nr to be consistent. > > Other than that, the patch looks good to me. Thank you for the review.
next prev parent reply other threads:[~2022-03-21 19:07 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-21 14:21 [RFC PATCH 0/5] Split a huge page to any lower order pages Zi Yan 2022-03-21 14:21 ` Zi Yan 2022-03-21 14:21 ` [RFC PATCH 1/5] mm: memcg: make memcg huge page split support any order split Zi Yan 2022-03-21 14:21 ` Zi Yan 2022-03-21 18:57 ` Roman Gushchin 2022-03-21 18:57 ` Roman Gushchin 2022-03-21 19:07 ` Zi Yan [this message] 2022-03-21 19:07 ` Zi Yan 2022-03-21 19:54 ` Matthew Wilcox 2022-03-21 19:54 ` Matthew Wilcox 2022-03-21 20:26 ` Zi Yan 2022-03-21 20:26 ` Zi Yan 2022-03-21 14:21 ` [RFC PATCH 2/5] mm: page_owner: add support for splitting to any order in split page_owner Zi Yan 2022-03-21 14:21 ` Zi Yan 2022-03-21 19:02 ` Roman Gushchin 2022-03-21 19:02 ` Roman Gushchin 2022-03-21 19:08 ` Zi Yan 2022-03-21 19:08 ` Zi Yan 2022-03-21 14:21 ` [RFC PATCH 3/5] mm: thp: split huge page to any lower order pages Zi Yan 2022-03-21 14:21 ` Zi Yan 2022-03-21 22:18 ` Roman Gushchin 2022-03-21 22:18 ` Roman Gushchin 2022-03-22 14:21 ` Zi Yan 2022-03-22 14:21 ` Zi Yan 2022-03-22 3:21 ` Miaohe Lin 2022-03-22 3:21 ` Miaohe Lin 2022-03-22 14:30 ` Zi Yan 2022-03-22 14:30 ` Zi Yan 2022-03-23 2:31 ` Miaohe Lin 2022-03-23 2:31 ` Miaohe Lin 2022-03-23 22:10 ` Zi Yan 2022-03-24 2:02 ` Miaohe Lin 2022-03-24 2:02 ` Miaohe Lin 2022-03-22 20:57 ` Yang Shi 2022-03-21 14:21 ` [RFC PATCH 4/5] mm: truncate: split huge page cache page to a non-zero order if possible Zi Yan 2022-03-21 14:21 ` Zi Yan 2022-03-21 22:32 ` Roman Gushchin 2022-03-21 22:32 ` Roman Gushchin 2022-03-22 14:19 ` Zi Yan 2022-03-22 14:19 ` Zi Yan 2022-03-23 6:40 ` [mm] 2757cee2d6: UBSAN:shift-out-of-bounds_in_include/linux/log2.h kernel test robot 2022-03-23 6:40 ` kernel test robot 2022-03-21 14:21 ` [RFC PATCH 5/5] mm: huge_memory: enable debugfs to split huge pages to any order Zi Yan 2022-03-21 14:21 ` Zi Yan 2022-03-21 22:23 ` Roman Gushchin 2022-03-21 22:23 ` Roman Gushchin
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=0001CABA-9436-4EFF-9C7F-F67300D09DA1@nvidia.com \ --to=ziy@nvidia.com \ --cc=cgroups@vger.kernel.org \ --cc=hughd@google.com \ --cc=kirill.shutemov@linux.intel.com \ --cc=linmiaohe@huawei.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-kselftest@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=roman.gushchin@linux.dev \ --cc=shuah@kernel.org \ --cc=shy828301@gmail.com \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.