From: Yinghai Lu <yinghai@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Tejun Heo <tj@kernel.org>, Russ Anderson <rja@sgi.com>,
Linux MM <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] memblock, numa: Binary search node id
Date: Thu, 15 Aug 2013 14:06:44 -0700 [thread overview]
Message-ID: <CAE9FiQUyGpmMP0VPE5ZrvDMLB-sdb0DzajGvB_KDt-ZnoJZhPg@mail.gmail.com> (raw)
In-Reply-To: <20130815134348.bb119a7987af0bb64ed77b7b@linux-foundation.org>
On Thu, Aug 15, 2013 at 1:43 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Wed, 14 Aug 2013 22:46:29 -0700 Yinghai Lu <yinghai@kernel.org> wrote:
>
>> Current early_pfn_to_nid() on arch that support memblock go
>> over memblock.memory one by one, so will take too many try
>> near the end.
>>
>> We can use existing memblock_search to find the node id for
>> given pfn, that could save some time on bigger system that
>> have many entries memblock.memory array.
>
> Looks nice. I wonder how much difference it makes.
Russ said he would test on his 256 nodes system, but looks he never
got chance.
Thanks
Yinghai
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-08-15 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 5:46 Yinghai Lu
2013-08-15 20:43 ` Andrew Morton
2013-08-15 21:06 ` Yinghai Lu [this message]
2013-08-15 21:37 ` Russ Anderson
2013-08-16 19:01 ` Russ Anderson
2013-08-16 19:15 ` Yinghai Lu
2013-08-16 19:31 ` Russ Anderson
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=CAE9FiQUyGpmMP0VPE5ZrvDMLB-sdb0DzajGvB_KDt-ZnoJZhPg@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rja@sgi.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