Subject: Re: memory size
To: None <tech-embed@netbsd.org>
From: Brian Rose <lists@brianrose.net>
List: tech-embed
Date: 08/09/2004 16:32:36
jc.sb wrote:
> Hi,
> Suppose I want to build netbsd for an internet appliance
> which has typical IPv4 routing features, for example as
> listed in a standard router like this..
> http://www.netgear.com/products/details/RP614.pgp?view=
> or like this..
> http://www.zcom.com.tw/product/product%20info/XI-2250.htm
>
>
> nat, ipfilter, web browser, dhcp, maybe smb, etc.
>
> How much flash mem does the kernel and minimal userland require
> for this kind of config using arm or mips. 2 megabytes bzipped?
> 4 megabytes bzipped? Then, how much RAM is required for
> unpacking & running.. 4 megabyte? 8 megabyte?
>
> For example taking evbarm, compiling in this config,
> and running on an eval card. What's the ballpark estimate.
>
> I have been attempting this with linux recently and have
> found that kernel + gnu libs is about 3x to 4x too big,
> using other clibs like uclibc gets it down to about 2x to
> 3x too big, compared to other embedded o/s.
>
> How much physical memory does a network-attached-storage
> kernel + userland require, for example.
>
> I also am curious how much of netbsd userland would require
> replacing with other apps, for example fully-featured dhcpd
> may need replacing with something else for size reasons, where
> fancy features are not required. In the linux world the
> udhcpd package is used with busybox.
>
> Anyone have a comment on this kind of target.
>
>
>
I don't have any data for this particular target, however I did manage to
get a non-trivial kernel+login and tools down to around 1MB compressed.
This was a full, multiuser kernel with a few tools for managing files.
This was done for an x86 target. I suspect that you could do the same for
the other processors. You should be able to use the same process to get
your small build.
http://www.bsdnewsletter.com/2003/09/Features102.html
--
Brian