Re: Threads Vs Forks in Embedded Environment
- From: "Maxim Yegorushkin" <maxim.yegorushkin@xxxxxxxxx>
- Date: 6 Sep 2006 00:36:19 -0700
abhisheksingh.bits@xxxxxxxxx wrote:
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:
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:
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.
If it is linux 2.6, pthread_create and fork use the same system call:
clone(). Threads and processes are represented by the same data
structure in the kernel, with the difference being that threads share
address space and some other resources, while processes don't. Although
libpthread is still required to support threads.
.
- Follow-Ups:
- Re: Threads Vs Forks in Embedded Environment
- From: abhisheksingh.bits@xxxxxxxxx
- Re: Threads Vs Forks in Embedded Environment
- References:
- Threads Vs Forks in Embedded Environment
- From: abhisheksingh.bits@xxxxxxxxx
- Threads Vs Forks in Embedded Environment
- Prev by Date: Re: (char *)0 vs NULL
- Next by Date: Re: Binary Tree On Disk (Rough Wave Library)
- Previous by thread: Re: Threads Vs Forks in Embedded Environment
- Next by thread: Re: Threads Vs Forks in Embedded Environment
- Index(es):
Relevant Pages
|