Changes between Version 8 and Version 9 of library_malloc

Timestamp:

Dec 6, 2014, 4:15:42 PM (11 years ago)

Author:

alain

Comment:

--

library_malloc

@@ -20 +20 @@
  == cluster selection ==
 
-The malloc() and free() functions below have the same semantic as the standard UNIX functions.
-The remote_malloc() function is a specific GIET-VM extension.
+The malloc() and free() functions below have the same semantic as the standard UNIX functions. The cluster where the memory is allocated is implicitely defined by the (x,y) coordinate of the processor running the calling task.
 
-Using the (x,y) arguments in the remote_malloc() function, the user application can explicitely select the cluster(x,y) where memory will be allocated. 
-If these arguments (x,y) are not defined, as in the malloc() function, the cluster is implicitely defined by the (x,y) coordinate of the processor running the calling task.
+The remote_malloc() function is a specific GIET-VM extension that allow the application to explicitely select the cluster(x,y) where physical memory will be allocated. 
+
 If there is no heap(x,y) defined in the selected cluster, or if there is no more space in the selected heap(x,y) segment, a NULL pointer is returned.
 
- == Available functions
+ == Available functions ==
 
  * '''void * malloc( unsigned int size )