Книга: Distributed operating systems
1.3.3. Bus-Based Multicomputers
1.3.3. Bus-Based Multicomputers
On the other hand, building a multicomputer (i.e., no shared memory) is easy. Each CPU has a direct connection to its own local memory. The only problem left is how the CPUs communicate with each other. Clearly, some interconnection scheme is needed here, too, but since it is only for CPU-to-CPU communication, the volume of traffic will be several orders of magnitude lower than when the interconnection network is also used for CPU-to-memory traffic.
In Fig. 1-7 we see a bus-based multicomputer. It looks topologically similar to the bus-based multiprocessor, but since there will be much less traffic over it, it need not be a high-speed backplane bus. In fact, it can be a much lower speed LAN (typically, 10-100 Mbps, compared to 300 Mbps and up for a backplane bus). Thus Fig. 1-7 is more often a collection of workstations on a LAN than a collection of CPU cards inserted into a fast bus (although the latter configuration is definitely a possible design).
Fig. 1-7. A multicomputer consisting of workstations on a LAN.
- 8.3 USB Bus Communication
- 1.3.1. Bus-Based Multiprocessors
- 1.3.4. Switched Multicomputers
- Chapter 16. Commercial products based on Linux, iptables and netfilter
- 11.1.3. Шина SMBus
- Text-Based Console Login
- GUI-Based Printer Configuration Quick Start
- Console-Based Monitoring
- Using ssh-keygen to Enable Key-Based Logins
- Address-Based Virtual Hosts
- Name-Based Virtual Hosts
- Fedora for Business