Threads Vs Forks in Embedded Environment

Hi group,

i am doing a project at motorola. i have to clone the client side mobile phone software update engine.what is better suited for an embedded environment......threads or forks:


Threads require support libraries, so extra space is required in flash memory.

Updation of libraries may also be required so this may increase the installation time.

Though threads share resources, in our case the sharing is not substantial.


Forks may have increased RAM requirement but it depends upon number of forks . Each fork has its own copy of all the segments of the update engine.

Can anyone provide me with a comparison of advantages and disadvantages of threads and forks for embedded environment.

Reply to
Loading thread data ...

OS is embedded Linux. The platform is based on a dual core architecture having an ARM11 core (Application Processor, AP) that handles all the application level functionalities and a Star Core DSP processor ( Base band Processor, BP), which handles all the modem functions. OTASU supports Jffs2, cramfs file system. other products supports MCU (MCORE) also

Reply to

Forked processes maynot always have its own copy of ALL the segments. Most ports of Linux will do a "copy-on-write" for a "page", i.e. a process will get its own copy of a page only if it modifies it.


formatting link

Reply to
Sandeep Dutta

so u mean that i sholud use forks as design alternative for my project ?

Reply to

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.