| Line 138... |
Line 138... |
|
|
If you create something basing on this my work, I'll be glad if you
|
If you create something basing on this my work, I'll be glad if you
|
provide information about my project (especially if you cite my
|
provide information about my project (especially if you cite my
|
article, after it is ready and published)
|
article, after it is ready and published)
|
|
|
EXPERIMENTAL 10Gb/s IMPLEMENTATION
|
EXPERIMENTAL "JUMBO FRAMES" BASED IMPLEMENTATION FOR 1Gb/s and 10GB/s LINKS
|
In the directory experimental_fade_10g you can find experimental
|
In the directory experimental_jumbo_frames_version you can find
|
version of my protocol, working with the 10Gb/s link on the
|
the experimental version of my protocol, working with the 10Gb/s link on the
|
KC705 board.
|
KC705 board and with 1Gb/s link on the Atlys board.
|
|
It uses longer "jumbo frames" with 8192 bytes of user data to transmit
|
|
data from the FPGA.
|
|
The high speed operation has exposed serious disadvantages of the previous
|
|
implementation. E.g. the concept of "sets" of packets has been dropped,
|
|
and instead packets are sequentially (modulo 2^32) numbered in the data
|
|
stream.
|
|
Additionally a possibility to send user defined commands (16-bit command
|
|
code, 32-bit command argument, 12-bytes return value (with 8 bytes defined
|
|
by the user)) to the FPGA.
|
The design has been initially tested, and is working, but it still
|
The design has been initially tested, and is working, but it still
|
needs some improvments.
|
needs some improvements.
|
Please note, that this version uses the "jumbo" frames,
|
After the cleanup, this approach will be ported also to the version
|
with 8192 bytes of user data in each packet (plus header).
|
working with standard frames.
|
Therefore it was necessary to make some changes in the kernel
|
|
driver.
|
|
working with standard frames.
|
|
