Top Document: comp.arch.storage FAQ 2/2 Previous Document: [8.1.1] Single ended vs differential Next Document: [8.1.3] SCSI-I vs SCSI-II vs SCSI-III See reader questions & answers on this topic! - Help others by sharing your knowledge From: (Device) Interfaces Asynchronous transfers mean that every single byte must be acknowledged before the next can be transfered. Synchronous means that the device sending data can drop a series of transfers onto the bus, toggling REQ or ACK (as appropriate), and then sit back and wait for the corresponding pulses to return from the other device. Async transfers, involving much more waiting, are correspondingly slower. 2-4 MB/sec are good values for async transfers. Sync transfer speeds are established during a negotiation between the initiator and target, but devices are not required to use the full speed they negotiate for. This speed represents the maximum burst rate your device will use. Common values are 5 and 10 MB/sec. In practice, virtually every modern device supports synchronous transfers, but some implementations are better than others. User Contributions:Top Document: comp.arch.storage FAQ 2/2 Previous Document: [8.1.1] Single ended vs differential Next Document: [8.1.3] SCSI-I vs SCSI-II vs SCSI-III Part1 - Part2 - Single Page [ Usenet FAQs | Web FAQs | Documents | RFC Index ] Send corrections/additions to the FAQ Maintainer: rdv@alumni.caltech.edu (Rodney D. Van Meter)
Last Update March 27 2014 @ 02:11 PM
|
Comment about this article, ask questions, or add new information about this topic: