On Oct 23 Peter Hurley wrote: > most controllers allow spillover into > the portion of bus cycle assigned for sync tx (which is another 4Kbytes > per 125us). All controllers do so and are expected to do so. Asynchronous traffic is not supposed to depend on a cycle master being active. > (Technical note: the actual total max for combined async > and sync tx is 6144 bytes per 125us clock) It depends on bus topology, transaction types, and more. For a single-hop S400 1394a bus (vulgo FireWire 400) I once calculated 44 MB/s bandwidth of asynchronous unified write transactions: http://marc.info/?l=linux1394-devel&m=109128028930225 That's at the physical layer; link layer and application layer performances are less than that of course. -- Stefan Richter -=====-===-- =-=- =-=== http://arcgraph.de/sr/ -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
