From: Roman Gushchin <guro@fb.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Rik van Riel <riel@surriel.com>,
Andrew Morton <akpm@linux-foundation.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <kernel-team@fb.com>,
Qian Cai <cai@lca.pw>, Mel Gorman <mgorman@techsingularity.net>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH] mm,page_alloc,cma: conditionally prefer cma pageblocks for movable allocations
Date: Wed, 11 Mar 2020 16:21:41 -0700 [thread overview]
Message-ID: <20200311232141.GA181064@carbon.DHCP.thefacebook.com> (raw)
In-Reply-To: <55f366be-ed3e-7b57-0fae-54845574d98a@suse.cz>
On Thu, Mar 12, 2020 at 12:03:58AM +0100, Vlastimil Babka wrote:
> On 3/11/20 11:58 PM, Roman Gushchin wrote:
> >>
> >> I agree it should be in the noise. But please do put it behind CONFIG_CMA
> >> #ifdef. My x86_64 desktop distro kernel doesn't have CONFIG_CMA. Even if this is
> >> effectively no-op with __rmqueue_cma_fallback() returning NULL immediately, I
> >> think the compiler cannot eliminate the two zone_page_state()'s which are
> >> atomic_long_read(), even if it's just ultimately READ_ONCE() here, that's a
> >> volatile cast which means elimination not possible AFAIK? Other architectures
> >> might be even more involved.
> >
> > I agree.
> >
> > Andrew,
> > can you, please, squash the following diff into the patch?
>
> Thanks,
>
> then please add to the result
>
> Acked-by: Vlastimil Babka <vbabka@suse.cz>
Thank you!
next prev parent reply other threads:[~2020-03-11 23:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 20:01 [PATCH] mm,page_alloc,cma: conditionally prefer cma pageblocks for movable allocations Rik van Riel
2020-03-07 22:38 ` Andrew Morton
2020-03-08 13:23 ` Rik van Riel
2020-03-11 17:58 ` Vlastimil Babka
2020-03-11 22:58 ` Roman Gushchin
2020-03-11 23:03 ` Vlastimil Babka
2020-03-11 23:21 ` Roman Gushchin [this message]
2020-03-11 8:51 ` Vlastimil Babka
2020-03-11 10:13 ` Joonsoo Kim
2020-03-11 17:41 ` Vlastimil Babka
2020-03-11 17:35 ` Roman Gushchin
2020-03-12 1:41 ` Joonsoo Kim
2020-03-12 2:39 ` Roman Gushchin
2020-03-12 8:56 ` Joonsoo Kim
2020-03-12 17:07 ` Roman Gushchin
2020-03-13 7:44 ` Joonsoo Kim
2020-04-02 2:13 ` Andrew Morton
2020-04-02 2:53 ` Roman Gushchin
2020-04-02 5:43 ` Joonsoo Kim
2020-04-02 19:42 ` Roman Gushchin
2020-04-03 4:34 ` Joonsoo Kim
2020-04-03 17:50 ` Roman Gushchin
2020-04-02 3:05 ` Roman Gushchin
2020-03-21 0:49 ` Minchan Kim
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=20200311232141.GA181064@carbon.DHCP.thefacebook.com \
--to=guro@fb.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=cai@lca.pw \
--cc=iamjoonsoo.kim@lge.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=riel@surriel.com \
--cc=vbabka@suse.cz \
/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).