[BusyBox] Using memory in daemons process

[JBS]

I have a uClinux kernel running in a Coldfire processor. And, yes,
this an no-MMU system.

I am using flat programs (not ELF) to run in my platform, and I obtain
.gdb to debug.

If I run: m68k-elf-nm --size-sort busybox.gdb

I have:

...... (a lot of small memory data)

000009f2 T _fpmaxtostr
00000a76 t colon
00000d02 T nfsmount
00001000 b comp_maskl
00001000 b comp_maskr
00001000 b key_perm_maskl
00001000 b key_perm_maskr
00001000 b lfile
00001000 b psbox
0000152a t do_cmd
00002000 b fp_maskl
00002000 b fp_maskr
00002000 b ip_maskl
00002000 b ip_maskr
00004000 b m_sbox

I suppose that the last data is the largest block memory I need. Whe I
run, for example syslogd I obtain in this case 384K but if I remove
applets I can run with only 41K. So, I made the question.

Thanks and best regards.


On 4/27/05, Rob Landley <rob at landley.net> wrote:
> On Sunday 24 April 2005 04:21 pm, JBS wrote:
> > We are using busybox for shell, syslogd, init and other background
> > programs.
> >
> > But we use also a lot of programas, like passwd, addgroup, cp, mv, etc.
> >
> > The problem is the more programs we need the more memory need every
> > background process.
> >
> > Is there a solution to use only the memory that every process need,
> > reducing the memory of daemon process.
> >
> > Thanks.
> 
> What environment are you using?  I presume you have no MMU, because in a
> system with an MMU physical memory generally isn't allocated until the page
> is touched.  (And zeroed out memory pages are multiple copy-on-write mappings
> of the zero page.)
> 
> That said, if you build a debug version (it's in the menuconfig options) and
> run "nm --size-sort" on the result, it should tell you who the biggest
> offenders are.  Then you can grep the source for the symbols...
> 
> Rob
>