Threads Vs Forks in Embedded Environment
- From: "abhisheksingh.bits@xxxxxxxxx" <abhisheksingh.bits@xxxxxxxxx>
- Date: 5 Sep 2006 23:01:17 -0700
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.
.
- Follow-Ups:
- Re: Threads Vs Forks in Embedded Environment
- From: Maxim Yegorushkin
- Re: Threads Vs Forks in Embedded Environment
- From: "Nils O. Selåsdal"
- Re: Threads Vs Forks in Embedded Environment
- Prev by Date: Re: (char *)0 vs NULL
- Next by Date: Re: (char *)0 vs NULL
- Previous by thread: Binary Tree On Disk (Rough Wave Library)
- Next by thread: Re: Threads Vs Forks in Embedded Environment
- Index(es):
Relevant Pages
|