Changes between Version 2 and Version 3 of library_malloc

Timestamp:

Aug 4, 2014, 5:30:24 PM (10 years ago)

Author:

alain

Comment:

--

library_malloc

@@ -10 +10 @@
 The distributed heap(x,y) segments must be explicitely defined in the application mapping.
 
- * For the '''malloc()''' function, the cluster selection is implicit: the (x,y) coordinate are defined by the coordinates of the processor running the calling task.
- * For the '''remote_malloc()''' function, the cluster selection is explicit: the (x,y) coordinates are arguments defined by the calling task 
+The malloc() and free() functions below have the same semantic as the standard UNIX functions.
+
+== cluster selection ==
+
+Using the '''(x,y)''' arguments (as in the remote_malloc() function below), the user application can explicitely select the allocator in cluster(x,y). 
+If these arguments (x,y) are not defined, (as in the malloc() function below), the cluster is implicitely defined by the (x,y) coordinate of the processor running the calling task.
+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.
+
+ == alignment ==
+
+Using the '''align''' arguments, the user application can require the  selected allocator to return a virtual address aligned on a power of 2 (1 << align).
+If the align argument value is larger than 31, a NULL pointer is returned.
 
  == Available functions
 
- * 
+ * '''void * malloc( unsigned int size )
+ * '''void * malloc_aligned( unsigned int size, unsigned int align )
+ * '''void * remote_malloc( unsigned int size, unsigned int x, unsigned int y )
+ * '''void * remote_malloc_aligned( unsigned int size, unsigned int align, unsigned int x, unsigned int y )
+ * '''void free( void* ptr ) 
+ 
+ == WARNING ==
+In the present implementation, the free() function cannot be used with the remote_malloc() and remote