[OpenWrt-Devel] [PATCH] toolchain/uClibc: add support of uClibc-ng
nbd at openwrt.org
Thu Aug 27 19:11:14 EDT 2015
On 2015-08-28 01:03, Adam Kuklycz wrote:
> Just following up on the suspected memory leak, and image build sizes.
> With the memory leak, it's not a memory leak as such rather than
> conntrackd filling things up with a log file.
> After 22 hours of running:
> root at gateway-openwrt:/tmp/log# ls -l
> -rw------- 1 root root 30080612 Aug 28 08:44
> drwxr-xr-x 2 root root 60 Aug 27 10:37 ddns
> -rw-r--r-- 1 root root 0 Aug 25 13:06 lastlog
> -rw-r--r-- 1 root root 0 Aug 27 10:36 log.nmbd
> -rw-r--r-- 1 root root 0 Aug 27 10:36 log.smbd
> -rw-r--r-- 1 root root 0 Aug 25 13:06 wtmp
> Deleting the log file and then shutting down conntrackd cleared the used
> space. I might look at omitting conntrackd from the builds in future.
> Now for the build sizes.
> musl does produce a larger image. Below is the result of a
> configuration file I have used for trunk builds with releases 457xx and
> have reused for a build on r46734 the only changes being I selected
> either uclibc or musl for the toolchain, otherwise the config file used
> is identical.
> -rw-r--r-- 1 adamk adamk 8126468 Aug 27 23:15
> -rw-r--r-- 1 adamk adamk 7864324 Aug 27 14:19
> Now, for stability sakes I'll want to reduce the image size anyway, with
> the bloat from latest kernels blowing things out by a good 300KB as
> well, but it looks like using musl adds around 300KB too.
> Have the devs determined that perhaps the increased performance of using
> musl outweighs the hit on image sizes?
Images are padded, often to 256 KB (which is the size increase of your
image). This means that it might be that musl just slightly increases
the image size enough to push it to the next 256KB boundary.
Comparing the size of
between uclibc and musl should be more accurate.
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
More information about the openwrt-devel