From: David Hildenbrand <david@redhat.com>
To: Hari Bathini <hbathini@linux.ibm.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org
Cc: mike.kravetz@oracle.com, mahesh@linux.ibm.com,
sourabhjain@linux.ibm.com, osalvador@suse.de
Subject: Re: [PATCH 1/2] mm/cma: provide option to opt out from exposing pages on activation failure
Date: Tue, 21 Dec 2021 19:48:05 +0100 [thread overview]
Message-ID: <e4748b18-3de3-b3f9-464a-e5cfcf9f05d4@redhat.com> (raw)
In-Reply-To: <20211220193419.104242-2-hbathini@linux.ibm.com>
On 20.12.21 20:34, Hari Bathini wrote:
> Commit 072355c1cf2d ("mm/cma: expose all pages to the buddy if
> activation of an area fails") started exposing all pages to buddy
> allocator on CMA activation failure. But there can be CMA users that
> want to handle the reserved memory differently on CMA allocation
> failure. Provide an option to opt out from exposing pages to buddy
> for such cases.
Can you elaborate why that is important and what the target user can
actually do with it?
It certainly cannot do CMA allocations :)
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-12-21 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 19:34 [PATCH 0/2] powerpc/fadump: handle CMA activation failure appropriately Hari Bathini
2021-12-20 19:34 ` [PATCH 1/2] mm/cma: provide option to opt out from exposing pages on activation failure Hari Bathini
2021-12-21 18:48 ` David Hildenbrand [this message]
2022-01-06 12:01 ` Hari Bathini
2022-01-11 14:36 ` David Hildenbrand
2022-01-12 9:50 ` Hari Bathini
2021-12-20 19:34 ` [PATCH 2/2] powerpc/fadump: opt out from freeing pages on cma " Hari Bathini
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=e4748b18-3de3-b3f9-464a-e5cfcf9f05d4@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hbathini@linux.ibm.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=mike.kravetz@oracle.com \
--cc=mpe@ellerman.id.au \
--cc=osalvador@suse.de \
--cc=sourabhjain@linux.ibm.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).