Changes between Version 25 and Version 26 of almosOnTsarDoc

Timestamp:

Aug 22, 2012, 3:33:54 PM (13 years ago)

Author:

almaless

Comment:

--

almosOnTsarDoc

@@ -126 +126 @@
 That is it ... you are done !!
 
-'''Note''': the kernel of ALMOS takes its own dynamic decisions about the management of the hardware resources including threads placement and cores load-balancing. Nevertheless, you can explicitly place the new process on a given core by using the ''-p core_number'' of the ''exec'' command (e.g. ''exec -p 3 /bin/hello''). This concerns only the first thread which executes the ''main()'' function. If you want to control the placement of the next threads, you can use the ''pthread_attr_setcpuid_np()'' function to set the core number on which the new thread will be pinned (e.g. ''DISTRIB/apps/bcv/main.c'').   
+'''Note''': the kernel of ALMOS takes its own dynamic decisions about the management of the hardware resources including threads placement and cores load-balancing. Nevertheless, you can explicitly place the new process on a given core by using the argument ''-p core_number'' of the ''exec'' command (e.g. ''exec -p 3 /bin/hello''). This concerns only the first thread which executes the ''main()'' function. If you want to control the placement of the next threads, you can use the ''pthread_attr_setcpuid_np()'' function to set the core number on which the new thread will be pinned (e.g. ''DISTRIB/apps/bcv/main.c'').   
 
 In a normal situation your application may have some bugs and you need to validate it. The recommended and most convenient method is to test and validate your application on Linux before corss-compiling it for ALMOS. Lets go back to ''DISTRIB/apps/hello_world'' and clean the directory before compiling the same application for Linux: