Changes between Version 18 and Version 19 of almosOnTsarDoc

Timestamp:

Aug 21, 2012, 2:00:27 PM (12 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 ''-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:
@@ -165 +165 @@
 
 == Running without the interactive mode ==
+As you may certainly noticed, the simulation speed is slow. This because the simulator is cycle and bit accurate, that is, the simulation includes the evolution of all hardware FSMs (Finite State Machine), data movements and contentions on all hardware resources at a cycle and bit precision.
 
+For a large TSAR configuration starting from ''sim16'' (i.e. 16 x 4 = 64 cores) or even if you just want to launch several instances of the simulator with different configurations, you need to disable the interactive mode in favor of a batch execution mode. This can be done by following 2 steps before running a simulation:
+
+ 1. Redirecting the simulator ttys output to files
+ 2. Write a mini script to let the shell automatically executes your programs
+
+
+    
 TBD ...