| | 1 | {{{ |
| | 2 | BOF 1: (INTER PROCESS COMMUNICATION) |
| | 3 | vulnerability issues in IPC (get/read/put) -- how can we prevent malicious users from corrupting the database? |
| | 4 | |
| | 5 | firewall issues -- certain clients will not be able to communicate. |
| | 6 | |
| | 7 | what type of applications can use this? |
| | 8 | cellular GAs? |
| | 9 | MPI applications -- not all MPI applications require tightly coupled processors, some have more appropriate computation to communication ratios. |
| | 10 | |
| | 11 | somewhat coupled applications |
| | 12 | load balancing -- appropriately balancing load can reduce inter client communication and maybe make IPC useful to some applications |
| | 13 | process migration -- can aid in load balancing |
| | 14 | latency detection -- grouping clients with low latency could allow group computation |
| | 15 | |
| | 16 | malaria control |
| | 17 | memory bound simulation can benefit from having a workunit split between hosts |
| | 18 | are communication requirements realistic? |
| | 19 | reduce communication with algorithm |
| | 20 | |
| | 21 | p2p communication bewteen clients |
| | 22 | |
| | 23 | distributed hashtables could be used for put/read/get |
| | 24 | |
| | 25 | put/read/get could use storage for checkpoints -- cliques can be used as well |
| | 26 | |
| | 27 | }}} |