Changes between Version 64 and Version 65 of WikiStart

Timestamp:

Nov 5, 2014, 5:37:36 PM (10 years ago)

Author:

alain

Comment:

--

WikiStart

@@ -7 +7 @@
 The GIET-VM assumes that the hardware architecture is structured as a 2D mesh of ''clusters''. There is one physical memory bank, and several processor cores per cluster. Each processor is identified by a composite index [x,y,p] where x, y are the cluster coordinates, and p is the local processor index. 
 
-It is written for the MIPS32 processor. The virtual adresses are on 32 bits and use the (unsigned int) type, but the physicals addresses can have up to 40 bits, and use the (unsigned long long) type.
+The GIET_VM is written for the MIPS32 processor. The virtual adresses are on 32 bits and use the (unsigned int) type. The physicals addresses can have up to 40 bits, and use the (unsigned long long) type.
 
-The GIET_VM supports a paged virtual memory, with two types of pages BPP (Big Physical Pages: 2 Mbytes), and SPP (Small Physical Pages: 4 Kbytes). The physical memory allocation is fully static, and all page tables (one page table per virtual space) are completely build and initialized in the boot phase. There is no page fault, and no swap on disk in the GIET_VM.
+The GIET_VM supports a paged virtual memory, with two types of pages BPP (Big Physical Pages: 2 Mbytes), and SPP (Small Physical Pages: 4 Kbytes). The physical memory allocation is fully static: all page tables (one page table per virtual space) are completely build and initialized in the boot phase. There is no page fault, and no swap on disk in the GIET_VM.
 
 The GIET_VM supports parallel multi-tasks user application. A GIET_VM user application is similar to a POSIX process: one virtual space per application. A task is similar to a Posix thread: all tasks in a given application share the same virtual space. Any task can be allocated to any processor, but the allocation is fully static : no task migration. Therefore, there is one private scheduler for each processor.