linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Chintan Pandya <cpandya@codeaurora.org>,
	devicetree@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 3/3] of: add early boot allocation of of_find_node_by_phandle() cache
Date: Mon, 5 Mar 2018 19:12:05 -0800	[thread overview]
Message-ID: <c5393057-b0e0-7e9d-041a-96996cf047b2@gmail.com> (raw)
In-Reply-To: <CAL_Jsq+sD=Hj+3cYy0injRSZ5Dj2M6c+KbiFrrwsO_9pqq8wKg@mail.gmail.com>

On 03/05/18 12:26, Rob Herring wrote:
> On Sun, Mar 4, 2018 at 6:14 PM,  <frowand.list@gmail.com> wrote:
>> From: Frank Rowand <frank.rowand@sony.com>
>>
>> The initial implementation of the of_find_node_by_phandle() cache
>> allocates the cache using kcalloc().  Add an early boot allocation
>> of the cache so it will be usable during early boot.  Switch over
>> to the kcalloc() based cache once normal memory allocation
>> becomes available.
> 
> Do we get a lot of lookups early? It makes sense to me to do early,
> but freeing and repopulating seems to add needless complexity.

Hey, that was my argument.  :-)

I would be quite happy leaving off patch 3/3.  And without 3/3,
2/3 becomes not necessary here, but still could go in separately
for completeness.  Though it could go in via Andrew.

-Frank

      reply	other threads:[~2018-03-06  3:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05  0:14 [PATCH v5 0/3] of: cache phandle nodes to reduce cost of of_find_node_by_phandle() frowand.list
2018-03-05  0:14 ` [PATCH v5 1/3] " frowand.list
2018-03-09 23:03   ` Rob Herring
2018-03-10  1:20     ` Frank Rowand
2018-06-12 18:16   ` Alan Tull
2018-06-13 14:42     ` Alan Tull
2018-06-13 21:47       ` Frank Rowand
2018-06-14 20:59         ` Alan Tull
2018-08-30  0:44   ` v4.17 regression: PowerMac G3 won't boot, was " Finn Thain
2018-08-30  1:05     ` Rob Herring
     [not found]       ` <569e4bc3-2149-4b2d-562f-e400dd05a8a8@yahoo.com>
2018-08-31  4:35         ` Benjamin Herrenschmidt
2018-08-31  4:49           ` Benjamin Herrenschmidt
2018-08-31  4:49           ` Benjamin Herrenschmidt
2018-08-31  4:36     ` Frank Rowand
2018-08-31  4:58       ` Benjamin Herrenschmidt
2018-09-09 17:04         ` Benjamin Herrenschmidt
2018-09-09 23:52           ` Frank Rowand
2018-09-10 12:53           ` Rob Herring
2018-09-11 15:53             ` Frank Rowand
     [not found]             ` <abb0dec2-da3a-2c04-0e9f-28851b22cf75@yahoo.com>
2018-09-12  0:15               ` Finn Thain
2018-03-05  0:14 ` [PATCH v5 2/3] memblock: add memblock_free() alloc when CONFIG_HAVE_MEMBLOCK is not set frowand.list
2018-03-06  0:00   ` Andrew Morton
2018-03-05  0:14 ` [PATCH v5 3/3] of: add early boot allocation of of_find_node_by_phandle() cache frowand.list
2018-03-05 20:26   ` Rob Herring
2018-03-06  3:12     ` Frank Rowand [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=c5393057-b0e0-7e9d-041a-96996cf047b2@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=cpandya@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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).