linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shivank Garg <shivankg@amd.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: pbonzini@redhat.com, corbet@lwn.net, akpm@linux-foundation.org,
	acme@redhat.com, namhyung@kernel.org, mpe@ellerman.id.au,
	isaku.yamahata@intel.com, joel@jms.id.au, kvm@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	bharata@amd.com, nikunj@amd.com
Subject: Re: [PATCH RFC 2/3] mm: Add mempolicy support to the filemap layer
Date: Tue, 17 Sep 2024 18:13:13 +0530	[thread overview]
Message-ID: <e471ad3c-daf1-4a21-b800-9934d1d3d9df@amd.com> (raw)
In-Reply-To: <ZuimLtrpv1dXczf5@casper.infradead.org>

Hello Matthew,

Thank you for the review comments.

On 9/17/2024 3:12 AM, Matthew Wilcox wrote:
> On Mon, Sep 16, 2024 at 04:57:42PM +0000, Shivank Garg wrote:

>> +static inline struct folio *filemap_grab_folio_mpol(struct address_space *mapping,
>> +					pgoff_t index, struct mempolicy *mpol)
>> +{
>> +	return __filemap_get_folio_mpol(mapping, index,
>> +			FGP_LOCK | FGP_ACCESSED | FGP_CREAT,
>> +			mapping_gfp_mask(mapping), mpol);
>> +}
> 
> This should be conditional on CONFIG_NUMA, just like 
> filemap_alloc_folio_mpol_noprof() above.

+#ifdef CONFIG_NUMA
 static inline struct folio *filemap_grab_folio_mpol(struct address_space *mapping,
                                        pgoff_t index, struct mempolicy *mpol)
 {
@@ -739,6 +742,13 @@ static inline struct folio *filemap_grab_folio_mpol(struct address_space *mappin
                        FGP_LOCK | FGP_ACCESSED | FGP_CREAT,
                        mapping_gfp_mask(mapping), mpol);
 }
+#else
+static inline struct folio *filemap_grab_folio_mpol(struct address_space *mapping,
+                                       pgoff_t index, struct mempolicy *mpol)
+{
+       return filemap_grab_folio(mapping, index);
+}
+#endif /* CONFIG_NUMA */

> 
>> @@ -1947,7 +1959,7 @@ struct folio *__filemap_get_folio(struct address_space *mapping, pgoff_t index,
>>  			err = -ENOMEM;
>>  			if (order > 0)
>>  				alloc_gfp |= __GFP_NORETRY | __GFP_NOWARN;
>> -			folio = filemap_alloc_folio(alloc_gfp, order);
>> +			folio = filemap_alloc_folio_mpol_noprof(alloc_gfp, order, mpol);
> 
> Why use the _noprof variant here?

I've defined the filemap_alloc_folio_mpol variant for using here:
+#define filemap_alloc_folio_mpol(...)                          \
+       alloc_hooks(filemap_alloc_folio_mpol_noprof(__VA_ARGS__))

+++ b/mm/filemap.c
@@ -1959,7 +1959,7 @@ struct folio *__filemap_get_folio_mpol(struct address_space *mapping, pgoff_t in
                        err = -ENOMEM;
                        if (order > 0)
                                alloc_gfp |= __GFP_NORETRY | __GFP_NOWARN;
-                       folio = filemap_alloc_folio_mpol_noprof(alloc_gfp, order, mpol);
+                       folio = filemap_alloc_folio_mpol(alloc_gfp, order, mpol);
                        if (!folio)
   

> 
>> diff --git a/mm/mempolicy.c b/mm/mempolicy.c
>> index 9e9450433fcc..88da732cf2be 100644
>> --- a/mm/mempolicy.c
>> +++ b/mm/mempolicy.c
>> @@ -2281,6 +2281,7 @@ struct folio *folio_alloc_mpol_noprof(gfp_t gfp, unsigned int order,
>>  	return page_rmappable_folio(alloc_pages_mpol_noprof(gfp | __GFP_COMP,
>>  							order, pol, ilx, nid));
>>  }
>> +EXPORT_SYMBOL(folio_alloc_mpol_noprof);
> 
> Why does this need to be exported?  What module will use itI've removed this EXPORT.

Thank you for the suggestion.
I overlooked those details and will post the replied changes in next version of this patchset.

Best Regards,
Shivank

  reply	other threads:[~2024-09-17 12:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16 16:57 [PATCH RFC 0/3] Add NUMA mempolicy support for KVM guest_memfd Shivank Garg
2024-09-16 16:57 ` [PATCH RFC 1/3] KVM: guest_memfd: Extend creation API to support NUMA mempolicy Shivank Garg
2024-09-16 16:57 ` [PATCH RFC 2/3] mm: Add mempolicy support to the filemap layer Shivank Garg
2024-09-16 21:42   ` Matthew Wilcox
2024-09-17 12:43     ` Shivank Garg [this message]
2024-09-16 16:57 ` [PATCH RFC 3/3] KVM: guest_memfd: Enforce NUMA mempolicy if available Shivank Garg

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=e471ad3c-daf1-4a21-b800-9934d1d3d9df@amd.com \
    --to=shivankg@amd.com \
    --cc=acme@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bharata@amd.com \
    --cc=corbet@lwn.net \
    --cc=isaku.yamahata@intel.com \
    --cc=joel@jms.id.au \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mpe@ellerman.id.au \
    --cc=namhyung@kernel.org \
    --cc=nikunj@amd.com \
    --cc=pbonzini@redhat.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: 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).