問題文
A read-based benchmark fails to start between two nodes even though a write-based one works. Which explanation is correct?
選択肢
- The read operation is available only in the reliable connected mode, so a connection set up in another mode cannot use it.
- The read operation requires the topology file to have been supplied, and the tool resolves the far side by name before it opens the connection for reading.
- The read operation requires the buffers on the far side to have been registered with write permission as well as read permission, which the write-based benchmark does implicitly and the read-based one does not, so the operator has to supply an additional argument for the registration to include both.
- The read operation is not supported by the fabric management entity, which has to authorize each operation type before it can be used, and it declines the request until then.