Re: Embedded linux: With or without MMU
- From: "Morten M. Jørgensen" <grinder213@xxxxxxxxx>
- Date: Fri, 8 Feb 2008 01:31:00 -0800 (PST)
AFAIK the API calls are quite different with µCLinux, but you never do
direct Linux API calls. You need to link your application against one of
the µC-aware libraries (instead of gLibC) and thus you will notice no
difference in "normal" applications. OK there is no "fork" and you need
to use vfork instead that works a bit different, but you supposedly will
not use fork a lot anyway in your own code in an embedded device. If you
want to do multitasking with your supposedly will use the pthread library.
In terms of MMU performance lack I guess that the pthread lib will do
best - since (AFAIK) multiple POSIX threads within the same
application will run in the same address space? a fork() call will
(AFAIK again) spawn a replicate of the process in another address
space - or is this assumption wrong?
Won't I run into problems when importing general Linux application
that I need in my systems - if I run uCLinux?
Supposedly µCLinux will boot faster than full Linux.
Again because of the lack of a virtuel memory system?
- Prev by Date: LTIB kernel booting problem
- Next by Date: Re: Embedded linux: With or without MMU
- Previous by thread: Re: Embedded linux: With or without MMU
- Next by thread: Re: Embedded linux: With or without MMU