From: David Hildenbrand <david@redhat.com>
To: Zi Yan <ziy@nvidia.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linuxppc-dev@lists.ozlabs.org,
Andrew Morton <akpm@linux-foundation.org>,
Oscar Salvador <osalvador@suse.de>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Naveen N Rao <naveen@kernel.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>
Subject: Re: [PATCH v1 0/6] mm/page_alloc: gfp flags cleanups for alloc_contig_*()
Date: Tue, 3 Dec 2024 09:29:48 +0100 [thread overview]
Message-ID: <dd45ff45-8894-4502-a4ee-ca4cd927662b@redhat.com> (raw)
In-Reply-To: <6CE8BCE0-BDBE-41BB-9998-D9165CF05A1F@nvidia.com>
On 02.12.24 23:07, Zi Yan wrote:
> On 2 Dec 2024, at 7:58, David Hildenbrand wrote:
>
>> Let's clean up the gfp flags handling, and support __GFP_ZERO, such that we
>> can finally remove the TODO in memtrace code.
>>
>> I did some alloc_contig_*() testing with virtio-mem and hugetlb; I did not
>> test powernv/memtrace -- I cross-compiled it, though.
>>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Cc: Oscar Salvador <osalvador@suse.de>
>> Cc: Zi Yan <ziy@nvidia.com>
>> Cc: Michael Ellerman <mpe@ellerman.id.au>
>> Cc: Nicholas Piggin <npiggin@gmail.com>
>> Cc: Christophe Leroy <christophe.leroy@csgroup.eu>
>> Cc: Naveen N Rao <naveen@kernel.org>
>> Cc: Madhavan Srinivasan <maddy@linux.ibm.com>
>
> FYI, linux-mm does not get any of your emails: https://lore.kernel.org/linux-mm/ECFA727B-F542-42E5-BE32-F9FB27F5DCDB@nvidia.com/, but linux-kernel has them.
Indeed, linuxppc seems to have them as well.
Guess I'll have to blame it on linux-mm, then ;)
Let me resend with #5 patch description adjusted. Thanks for the review!
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2024-12-03 8:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 12:58 [PATCH v1 0/6] mm/page_alloc: gfp flags cleanups for alloc_contig_*() David Hildenbrand
2024-12-02 12:58 ` [PATCH v1 1/6] mm/page_isolation: don't pass gfp flags to isolate_single_pageblock() David Hildenbrand
2024-12-02 18:08 ` Zi Yan
2024-12-02 12:58 ` [PATCH v1 2/6] mm/page_isolation: don't pass gfp flags to start_isolate_page_range() David Hildenbrand
2024-12-02 18:09 ` Zi Yan
2024-12-02 12:58 ` [PATCH v1 3/6] mm/page_alloc: make __alloc_contig_migrate_range() static David Hildenbrand
2024-12-02 18:13 ` Zi Yan
2024-12-02 12:58 ` [PATCH v1 4/6] mm/page_alloc: sort out the alloc_contig_range() gfp flags mess David Hildenbrand
2024-12-02 18:25 ` Zi Yan
2024-12-02 12:58 ` [PATCH v1 5/6] mm/page_alloc: forward the gfp flags from alloc_contig_range() to post_alloc_hook() David Hildenbrand
2024-12-02 18:33 ` Zi Yan
2024-12-02 12:58 ` [PATCH v1 6/6] powernv/memtrace: use __GFP_ZERO with alloc_contig_pages() David Hildenbrand
2024-12-02 22:07 ` [PATCH v1 0/6] mm/page_alloc: gfp flags cleanups for alloc_contig_*() Zi Yan
2024-12-03 8:29 ` David Hildenbrand [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=dd45ff45-8894-4502-a4ee-ca4cd927662b@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=osalvador@suse.de \
--cc=ziy@nvidia.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;
as well as URLs for NNTP newsgroup(s).