From: Wei Yang <richard.weiyang@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Wei Yang <richard.weiyang@gmail.com>,
mhocko@suse.com, tj@kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm/page_alloc: break on the first hit of mem range
Date: Wed, 28 Mar 2018 11:44:34 +0800 [thread overview]
Message-ID: <20180328034434.GB94065@WeideMacBook-Pro.local> (raw)
In-Reply-To: <20180327183757.f66f5fc200109c06b7a4b620@linux-foundation.org>
On Tue, Mar 27, 2018 at 06:37:57PM -0700, Andrew Morton wrote:
>On Wed, 28 Mar 2018 08:51:42 +0800 Wei Yang <richard.weiyang@gmail.com> wrote:
>
>> On Tue, Mar 27, 2018 at 03:47:40PM -0700, Andrew Morton wrote:
>> >On Tue, 27 Mar 2018 11:57:07 +0800 Wei Yang <richard.weiyang@gmail.com> wrote:
>> >
>> >> find_min_pfn_for_node() iterate on pfn range to find the minimum pfn for a
>> >> node. The memblock_region in memblock_type are already ordered, which means
>> >> the first hit in iteration is the minimum pfn.
>> >>
>> >> This patch returns the fist hit instead of iterating the whole regions.
>> >>
>> >> ...
>> >>
>> >> --- a/mm/page_alloc.c
>> >> +++ b/mm/page_alloc.c
>> >> @@ -6365,14 +6365,14 @@ unsigned long __init node_map_pfn_alignment(void)
>> >> /* Find the lowest pfn for a node */
>> >> static unsigned long __init find_min_pfn_for_node(int nid)
>> >> {
>> >> - unsigned long min_pfn = ULONG_MAX;
>> >> - unsigned long start_pfn;
>> >> + unsigned long min_pfn;
>> >> int i;
>> >>
>> >> - for_each_mem_pfn_range(i, nid, &start_pfn, NULL, NULL)
>> >> - min_pfn = min(min_pfn, start_pfn);
>> >> + for_each_mem_pfn_range(i, nid, &min_pfn, NULL, NULL) {
>> >> + break;
>> >> + }
>> >
>> >That would be the weirdest-looking code snippet in mm/!
>> >
>>
>> You mean the only break in a for_each loop? Hmm..., this is really not that
>> nice. Haven't noticed could get a "best" in this way :-)
>
>I guess we can make it nicer by adding a comment along the lines of
>
> /*
> * Use for_each_mem_pfn_range() to locate the lowest valid pfn in the
> * range. We only need to iterate a single time, as the pfn's are
> * sorted in ascending order.
> */
>
>Because adding a call to the obviously-internal __next_mem_pfn_range()
>isn't very nice either.
Yep, you are right.
>
>Anyway, please have a think, see what we can come up with.
My approach is to add a macro fist_mem_pfn() as a self-explain wrapper of
__next_mem_pfn_range().
Hope you would like this :-)
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2018-03-28 3:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 3:57 [PATCH] mm/page_alloc: break on the first hit of mem range Wei Yang
2018-03-27 10:58 ` Michal Hocko
2018-03-28 0:39 ` Wei Yang
2018-03-28 7:02 ` Michal Hocko
2018-03-28 13:17 ` Wei Yang
2018-03-27 22:47 ` Andrew Morton
2018-03-28 0:51 ` Wei Yang
2018-03-28 1:37 ` Andrew Morton
2018-03-28 3:44 ` Wei Yang [this message]
2018-03-28 3:47 ` [PATCH] mm/page_alloc: optimize find_min_pfn_for_node() by geting the minimal pfn directly Wei Yang
2018-03-28 11:58 ` Michal Hocko
2018-03-28 13:34 ` Wei Yang
2018-03-28 14:02 ` Michal Hocko
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=20180328034434.GB94065@WeideMacBook-Pro.local \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=tj@kernel.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).