From: Hanjun Guo <guohanjun@huawei.com>
To: Jia He <hejianet@gmail.com>, Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Will Deacon <will.deacon@arm.com>,
Ard Biesheuvel <ard.biesheuvel@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Michal Hocko <mhocko@suse.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Kemi Wang <kemi.wang@intel.com>,
Wei Yang <richard.weiyang@gmail.com>,
Linux-MM <linux-mm@kvack.org>,
Eugeniu Rosca <erosca@de.adit-jv.com>,
Petr Tesarik <ptesarik@suse.com>,
Nikolay Borisov <nborisov@suse.com>,
Russell King <linux@armlinux.org.uk>,
Daniel Jordan <daniel.m.jordan@oracle.com>,
"AKASHI Takahiro" <takahiro.akashi@linaro.org>,
Mel Gorman <mgorman@suse.de>,
"Andrey Ryabinin" <aryabinin@virtuozzo.com>,
Laura Abbott <labbott@redhat.com>,
"Daniel Vacek" <neelx@redhat.com>,
Vladimir Murzin <vladimir.murzin@arm.com>,
"Kees Cook" <keescook@chromium.org>,
Vlastimil Babka <vbabka@suse.cz>,
"Johannes Weiner" <hannes@cmpxchg.org>,
YASUAKI ISHIMATSU <yasu.isimatu@gmail.com>,
"Jia He" <jia.he@hxt-semitech.com>,
Gioh Kim <gi-oh.kim@profitbricks.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Steve Capper <steve.capper@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
James Morse <james.morse@arm.com>,
"Philip Derrin" <philip@cog.systems>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v11 0/3] remain and optimize memblock_next_valid_pfn on arm and arm64
Date: Wed, 12 Jun 2019 20:48:57 +0800 [thread overview]
Message-ID: <ed84966f-81ed-3be9-5b21-1fd92deea3cc@huawei.com> (raw)
In-Reply-To: <8fdf5545-21b7-354c-4c4b-e1e92048864f@gmail.com>
On 2019/6/12 9:05, Jia He wrote:
>>
>>> So what I would like to see is the patch set being proposed again,
>>> with the new data points added for documentation. Also, the commit
>>> logs need to crystal clear about how the meaning of PFN validity
>>> differs between ARM and other architectures, and why the assumptions
>>> that the optimization is based on are guaranteed to hold.
>> I think Jia He no longer works for HXT, if don't mind, I can repost
>> this patch set with Jia He's authority unchanged.
> Ok, I don't mind that, thanks for your followup :)
That's great, I will prepare a new version with Ard's comments addressed
then repost.
Thanks
Hanjun
prev parent reply other threads:[~2019-06-12 12:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 3:07 Jia He
2018-08-22 3:07 ` [PATCH v11 1/3] arm: arm64: introduce CONFIG_HAVE_MEMBLOCK_PFN_VALID Jia He
2018-08-22 3:07 ` [PATCH v11 2/3] mm: page_alloc: remain memblock_next_valid_pfn() on arm/arm64 Jia He
2018-08-22 3:07 ` [PATCH v11 3/3] mm: page_alloc: reduce unnecessary binary search in memblock_next_valid_pfn Jia He
2018-09-05 21:57 ` [PATCH v11 0/3] remain and optimize memblock_next_valid_pfn on arm and arm64 Andrew Morton
2018-09-06 10:47 ` Will Deacon
2018-09-06 11:24 ` Ard Biesheuvel
2018-09-07 14:44 ` Will Deacon
2018-09-14 18:50 ` Eugeniu Rosca
2019-06-08 4:22 ` Hanjun Guo
2019-06-10 13:16 ` Ard Biesheuvel
2019-06-11 15:18 ` Hanjun Guo
2019-06-12 1:05 ` Jia He
2019-06-12 12:48 ` Hanjun Guo [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=ed84966f-81ed-3be9-5b21-1fd92deea3cc@huawei.com \
--to=guohanjun@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=aryabinin@virtuozzo.com \
--cc=catalin.marinas@arm.com \
--cc=daniel.m.jordan@oracle.com \
--cc=erosca@de.adit-jv.com \
--cc=gi-oh.kim@profitbricks.com \
--cc=hannes@cmpxchg.org \
--cc=hejianet@gmail.com \
--cc=james.morse@arm.com \
--cc=jia.he@hxt-semitech.com \
--cc=keescook@chromium.org \
--cc=kemi.wang@intel.com \
--cc=labbott@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=nborisov@suse.com \
--cc=neelx@redhat.com \
--cc=philip@cog.systems \
--cc=ptesarik@suse.com \
--cc=richard.weiyang@gmail.com \
--cc=steve.capper@arm.com \
--cc=takahiro.akashi@linaro.org \
--cc=vbabka@suse.cz \
--cc=vladimir.murzin@arm.com \
--cc=will.deacon@arm.com \
--cc=yasu.isimatu@gmail.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