[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130527.151744.1526437556583356156.davem@davemloft.net>
Date: Mon, 27 May 2013 15:17:44 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: benh@...nel.crashing.org
Cc: arnd@...db.de, linuxppc-dev@...ts.ozlabs.org,
sebastian.hesselbarth@...il.com, andrew@...n.ch,
jason@...edaemon.net, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, buytenh@...tstofly.org,
grant.likely@...aro.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/2] ARM: kirkwood: proper retain MAC address
workaround on DT ethernet
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
Date: Tue, 28 May 2013 07:50:06 +1000
> On Mon, 2013-05-27 at 14:47 +0200, Arnd Bergmann wrote:
>> On Monday 27 May 2013 21:50:04 Benjamin Herrenschmidt wrote:
>> > However, that wouldn't help much with the allocation/leak problem,
>> > though at least it would be easier to use. It could also *try* to re-use
>> > the current allocation if the new content is of smaller or equal size.
>>
>> I thought that dtc tried to aggressively save space by folding identical
>> strings. If you tried to reuse a property that had its contents shared
>> with another one, you would get interesting results I guess.
>
> It used to be only property names, unless that has changed in recent
> dtc. But that's a good point, we probably want a flag in struct property
> like we have for nodes, indicating whether it comes from the original
> fdt data pool or not.
This is similar to what the "OF_IS_DYNAMIC()" thing on sparc
indicates.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists