<div dir="auto"><div>Hi Khem,</div><div dir="auto"><br></div><div dir="auto">I have no experience with musl but keen to understand does musl improves/impacts DRAM performance as compared to glibc? </div><div dir="auto"><br></div><div dir="auto">regards</div><div dir="auto">Ankur</div><div dir="auto"><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Wed, 27 Nov 2019, 7:17 a.m. Khem Raj, <<a href="mailto:raj.khem@gmail.com" target="_blank" rel="noreferrer">raj.khem@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, 2019-11-25 at 23:10 +0200, Adrian Bunk wrote:<br>
> On Mon, Nov 25, 2019 at 07:26:58PM +0000, Ross Burton wrote:<br>
> > On 25/11/2019 18:37, Ankur Tyagi wrote:<br>
> > > Hi,<br>
> > > <br>
> > > Based upon "thud" branch, I created core-image-minimal for<br>
> > > am335x-evm<br>
> > > board and resulting image size is very big(71M)<br>
> > <br>
> > If disk size is important then a good first step is to use musl<br>
> > instead of<br>
> > glibc:<br>
> > <br>
> > TCLIBC = "musl"<br>
> > ...<br>
> <br>
> musl is mainly useful for tiny systems, a 40 MB partition is such a<br>
> huge<br>
> amount of space that the size of the C library no longer matters<br>
> much.<br>
> <br>
> The size benefit of replacing glibc with musl is around 2 MB.<br>
<br>
I would refrain from labeling as useful for tiny systems. since<br>
static size is one thing, there is DRAM behaviour which is equally<br>
important, how malloc and other resource oriented algorithms behave is<br>
important as well.<br>
<br>
secondly, if I have 40MB partition, one might rather want to use extra<br>
space for implementing features in their product than spend it for<br>
enabling the system if they can.<br>
<br>
there are many other design considerations where musl might make more<br>
sense<br>
<br>
> <br>
> A partition with an -Os build of Yocto with glibc+systemd (sic)<br>
> is around 9 MB, together with bootloader and kernel this all<br>
> fits in a 16 MB flash. Use compression for kernel and root<br>
> filesystem and everything fits in a 8 MB flash.<br>
> <br>
<br>
-Os is not as well tested option as -O2 is. So we should always<br>
recommend it with grain of salt, speaking from experience there are<br>
bugs that will show up with Os which you wont see with O2 and leave a<br>
bad taste for user<br>
<br>
> > Ross<br>
> <br>
> cu<br>
> Adrian<br>
<br>
-- <br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" rel="noreferrer noreferrer" target="_blank">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer noreferrer noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</blockquote></div></div></div>