Difference: MemBUS (2 vs. 3)
Revision 32008-03-11 - GeorgiosTsoukalas
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
The Memory Bandwidth aware Userspace Scheduler (MemBUS) | ||||||||
| Line: 12 to 12 | ||||||||
The policy has been implemented in userspace, as the Memory Bandwidth aware Userpace Scheduler (MemBUS). Scheduling decisions are enforced with a combination of the perfctr performance-monitoring framework, the ptrace() Linux system call and standard UNIX SIGSTOP / SIGCONT signaling. | ||||||||
| Changed: | ||||||||
| < < | Later on, MemBUS was expanded (ICPADS 2006) so as to allow for cluster-wide gang scheduling; context switches are coordinated so that all peer processes belonging to the same job are scheduled simultaneously across the cluster, while trying to minimize interference due to contention for access to main memory and to the NIC on each node. | |||||||
| > > | Later on, MemBUS was expanded [ICPADS 2006] so as to allow for cluster-wide gang scheduling; context switches are coordinated so that all peer processes belonging to the same job are scheduled simultaneously across the cluster, while trying to minimize interference due to contention for access to main memory and to the NIC on each node. | |||||||
Publications
| ||||||||
View topic | History: r5 < r4 < r3 < r2 | More topic actions...
