From: hejianet@gmail.com (Jia He)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 5/5] mm: page_alloc: reduce unnecessary binary search in early_pfn_valid()
Date: Mon, 2 Apr 2018 16:15:09 +0800 [thread overview]
Message-ID: <75088758-f59c-c65a-6e88-116c1e6b6675@gmail.com> (raw)
In-Reply-To: <CAKv+Gu9jSXq7YN68Mk7WV4+aLr=nRtHmuQnHMdM8YhgeA-SYsg@mail.gmail.com>
On 4/2/2018 3:00 PM, Ard Biesheuvel Wrote:
> How much does it improve the performance? And in which cases?
>
> I guess it improves boot time on systems with physical address spaces
> that are sparsely populated with DRAM, but you really have to quantify
> this if you want other people to care.
Yes, I write the performance in patch 0/5. I will write it in the patch
description later.
--
Cheers,
Jia
prev parent reply other threads:[~2018-04-02 8:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 2:30 [PATCH v5 0/5] optimize memblock_next_valid_pfn and early_pfn_valid on arm and arm64 Jia He
2018-04-02 2:30 ` [PATCH v5 1/5] mm: page_alloc: remain memblock_next_valid_pfn() " Jia He
2018-04-02 6:55 ` Ard Biesheuvel
2018-04-02 7:49 ` Jia He
2018-04-02 7:53 ` Ard Biesheuvel
2018-04-03 3:07 ` Jia He
2018-04-11 4:47 ` Jia He
2018-04-02 7:50 ` kbuild test robot
2018-04-02 2:30 ` [PATCH v5 2/5] arm: arm64: page_alloc: reduce unnecessary binary search in memblock_next_valid_pfn() Jia He
2018-04-02 6:57 ` Ard Biesheuvel
2018-04-02 8:43 ` Daniel Vacek
2018-04-02 8:01 ` Daniel Vacek
2018-04-02 15:07 ` kbuild test robot
2018-04-02 2:30 ` [PATCH v5 3/5] mm/memblock: introduce memblock_search_pfn_regions() Jia He
2018-04-02 6:57 ` Ard Biesheuvel
2018-04-02 2:30 ` [PATCH v5 4/5] arm64: introduce pfn_valid_region() Jia He
2018-04-02 6:59 ` Ard Biesheuvel
2018-04-02 18:53 ` kbuild test robot
2018-04-02 2:30 ` [PATCH v5 5/5] mm: page_alloc: reduce unnecessary binary search in early_pfn_valid() Jia He
2018-04-02 7:00 ` Ard Biesheuvel
2018-04-02 8:15 ` Jia He [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=75088758-f59c-c65a-6e88-116c1e6b6675@gmail.com \
--to=hejianet@gmail.com \
--cc=linux-arm-kernel@lists.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).