From: Zi Yan <ziy@nvidia.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Hildenbrand <david@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Vlastimil Babka <vbabka@suse.cz>,
Mel Gorman <mgorman@techsingularity.net>,
Eric Ren <renzhengeek@gmail.com>, Mike Rapoport <rppt@kernel.org>,
Oscar Salvador <osalvador@suse.de>,
Christophe Leroy <christophe.leroy@csgroup.eu>
Subject: Re: [PATCH v11 0/6] Use pageblock_order for cma and alloc_contig_range alignment.
Date: Mon, 09 May 2022 21:07:20 -0400 [thread overview]
Message-ID: <7F381222-1C5C-4CBD-B29F-BBE0305231AD@nvidia.com> (raw)
In-Reply-To: <20220509180356.24ff0403cf3ffc3fd01ffe98@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 952 bytes --]
On 9 May 2022, at 21:03, Andrew Morton wrote:
> On Mon, 25 Apr 2022 10:31:12 -0400 Zi Yan <zi.yan@sent.com> wrote:
>
>> This patchset tries to remove the MAX_ORDER-1 alignment requirement for CMA
>> and alloc_contig_range(). It prepares for my upcoming changes to make
>> MAX_ORDER adjustable at boot time[1].
>
> I'm thinking this looks ready to be merged into mm-stable later this week, for
> the 5.19-rc1 merge window.
>
> I believe the build error at
> https://lkml.kernel.org/r/CA+G9fYveMF-NU-rvrsbaora2g2QWxrkF7AWViuDrJyN9mNScJg@mail.gmail.com
> was addressed in ARM?
Right. The warning is caused by CONFIG_ARM64_SME=y not this patchset,
see https://lore.kernel.org/all/YnGrbEt3oBBTly7u@qian/.
>
> I have one -fix to be squashed,
> https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-make-alloc_contig_range-work-at-pageblock-granularity-fix.patch
Yes. Thanks.
--
Best Regards,
Yan, Zi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]
prev parent reply other threads:[~2022-05-10 1:07 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 14:31 [PATCH v11 0/6] Use pageblock_order for cma and alloc_contig_range alignment Zi Yan
2022-04-25 14:31 ` [PATCH v11 1/6] mm: page_isolation: move has_unmovable_pages() to mm/page_isolation.c Zi Yan
2022-04-25 14:31 ` [PATCH v11 2/6] mm: page_isolation: check specified range for unmovable pages Zi Yan
2022-04-25 14:31 ` [PATCH v11 3/6] mm: make alloc_contig_range work at pageblock granularity Zi Yan
2022-04-29 13:54 ` Zi Yan
2022-05-24 19:00 ` Zi Yan
2022-05-25 17:41 ` Doug Berger
2022-05-25 17:53 ` Zi Yan
2022-05-25 21:03 ` Doug Berger
2022-05-25 21:11 ` Zi Yan
2022-05-26 17:34 ` Zi Yan
2022-05-26 19:46 ` Doug Berger
2022-04-25 14:31 ` [PATCH v11 4/6] mm: page_isolation: enable arbitrary range page isolation Zi Yan
2022-05-24 19:02 ` Zi Yan
2022-04-25 14:31 ` [PATCH v11 5/6] mm: cma: use pageblock_order as the single alignment Zi Yan
2022-04-25 14:31 ` [PATCH v11 6/6] drivers: virtio_mem: use pageblock size as the minimum virtio_mem size Zi Yan
2022-04-26 20:18 ` [PATCH v11 0/6] Use pageblock_order for cma and alloc_contig_range alignment Qian Cai
2022-04-26 20:26 ` Zi Yan
2022-04-26 21:08 ` Qian Cai
2022-04-26 21:38 ` Zi Yan
2022-04-27 12:41 ` Qian Cai
2022-04-27 13:10 ` Qian Cai
2022-04-27 13:27 ` Qian Cai
2022-04-27 13:30 ` Zi Yan
2022-04-27 21:04 ` Zi Yan
2022-04-28 12:33 ` Qian Cai
2022-04-28 12:39 ` Zi Yan
2022-04-28 16:19 ` Qian Cai
2022-04-29 13:38 ` Zi Yan
2022-05-19 20:57 ` Qian Cai
2022-05-19 21:35 ` Zi Yan
2022-05-19 23:24 ` Zi Yan
2022-05-20 11:30 ` Qian Cai
2022-05-20 13:43 ` Zi Yan
2022-05-20 14:13 ` Zi Yan
2022-05-20 19:41 ` Qian Cai
2022-05-20 21:56 ` Zi Yan
2022-05-20 23:41 ` Qian Cai
2022-05-22 16:54 ` Zi Yan
2022-05-22 19:33 ` Zi Yan
2022-05-24 16:59 ` Qian Cai
2022-05-10 1:03 ` Andrew Morton
2022-05-10 1:07 ` Zi Yan [this message]
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=7F381222-1C5C-4CBD-B29F-BBE0305231AD@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=christophe.leroy@csgroup.eu \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=osalvador@suse.de \
--cc=renzhengeek@gmail.com \
--cc=rppt@kernel.org \
--cc=vbabka@suse.cz \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).