Memory allocation sequence to non dialog work processes in SAP

What is the memory allocation sequence to non-dialog work processes (background, update, en-queue and spool work processes in SAP?
What are the SAP parameters used to define initial roll area, extended memory, heap memory, roll area ?
What is the memory allocation sequence to non dialog work processes in Windows NT?

Memory allocation sequence to dialog work processes is same in SAP for all the platforms.
However memory allocation sequence to non-dialog work processes is bit different based on Platform. In Windows NT, memory allocation sequence for non-dialog work processes is same as that of dialog work process memory allocation sequence in other platforms.
Memory allocation sequence to non dialog work processes in SAP as below (except in windows NT):

1. Initially memory is assigned from the Roll memory. Roll memory is defined by SAP parameter ztta/roll_area and it is assigned until it is completely used up.If the roll memory is full then 
2. Heap memory is allocated to the non-dialog work process. Heap memory is available until one of the following occurs : 
3. Either the limit of the heap memory for non-dialog work processes is reached (defined by the SAP parameter abap/heap_area_nondia) or the entire heap memory of all work processes of an SAP application server reaches its limit which is defined by parameter abap/heap_area_total. 
4. Operating system limits of allocating memory 
5. The swap space in the host system is completely used up. However this situation should not occur often which results in severe performance issues.

Please check swap space requirements for various platforms and please define swap space optimally to avoid this issue.
If all the above mentioned heap memory is completely used up then a non-dialog work process can use the SAP extended memory defined by SAP parameter em/initial_size_MB.