Hi Henning,<br><br>Thanks for the reply. I have got the info I was looking for.<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
sounds interesting, what kind of OS is this?</blockquote><div> [kalpesh] vxworks<br></div><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
To what kind of global variables do you refer to? In the shared memory the<br>
access to the data is guarded by the internal memory manager. You find it in<br>
the mem/shm_mem.{c,h} files.</blockquote><div> [kalpesh] I am referring to the variables which are global by their scope, declared outside<br>any function body.<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<div class="Ih2E3d"><br>
> So,after fork parent and child both interprete global data differently or<br>
> is there any design rule enforced that after fork no.process<br>
> will be writing global data. (igonre the cleanup for a while). Will there<br>
> be any any problem if I dont give child task its own copy of<br>
> global variables and let them use the same copy as parent?<br>
</div></blockquote><div> [kalpesh] I meant: <br> consider global variable is_main. The interpretation of this variable is different in<br> main process and the rest of the children it forks. I am looking the code into more <br>
details for other such type of global vars to achieve the objective of converting <br> processes to threads.<br><br> Regards,<br> Kalpesh<br></div></div><br><br>