Hi Michael,
Michael Schnell wrote:
I just have my first running uCLinux system in front of me (not created
by myself, but using a Kernel image and roof file system I got with the
hardware.
Of course I see that multiple programs are included in busybox.
This seems to be true for the command line interpreter, too.
Now the command line interpreter of course starts multiple other
programs that are done in busybox as well. (Of course there are other
possibilities top have the same program run multiple times, as well).
This system does not have shared libraries, so the programs are quite big.
Is the system smart enough not to load the program's "text" code pages
from the file system into RAM multiple times, but use the already loaded
instance and have it just use a different data page ?
Primarily this depends on whether your architecture supports
Execute-In-Place (XIP).
(If not the busybox paradigm does not seem very useful for systems
without shared libraries.)
No its not :-)
It is not shared libraries that is the problem as such, though
they are nice too.
With any non-MMU environment big binaries are more problematic.
You need to find large contiguous regions to bring them in (assuming
you cannot run them XIP from within the filesystem they are in).
Small is better.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Chief Software Dude EMAIL: [EMAIL PROTECTED]
Secure Computing Corporation PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
