by support »
Hi,
This figure (5 ms in your example) is explained in the stream's edit form: It's the approximate buffering time, and it has nothing to do with latency. The help button in the edit form supplies more information, as well as this page:
http://xillybus.com/doc/xillybus-latencyBy the way, a 32 bit interface has no chance of giving 1280 MB/s, because the interface uses a clock of 250 MHz at most, so there's a limit of 1 GB/s, but effectively you'll usually get something like 800 MB/s. If you're using a Revision B core, you need to make the data vector wider, or add more streams to get an aggregate bandwidth > 800 MB/s.
Regards,
Eli
Hi,
This figure (5 ms in your example) is explained in the stream's edit form: It's the approximate buffering time, and it has nothing to do with latency. The help button in the edit form supplies more information, as well as this page:
http://xillybus.com/doc/xillybus-latency
By the way, a 32 bit interface has no chance of giving 1280 MB/s, because the interface uses a clock of 250 MHz at most, so there's a limit of 1 GB/s, but effectively you'll usually get something like 800 MB/s. If you're using a Revision B core, you need to make the data vector wider, or add more streams to get an aggregate bandwidth > 800 MB/s.
Regards,
Eli