How many clock cycles are needed to produce the current running disparity on the TX and the RX?
RXRUNDISP
For RXRUNDISP, there is no latency for the disparity. The disparity shown on this port is aligned to whatever data bytes are displayed on RXDATA.
TXRUNDISP
There is a latency between TXDATA and TXRUNDISP as the disparity cannot be known ahead of time. The latency arises due to the data going through the CRC (if enabled) and 8b/10b encoder. It is only after your data bytes have passed through the 8b/10b encoder that TXRUNDISP reflects the running disparity for that particular set of bytes.
For estimates of the latency, refer to Table 2-6 in the RocketIO Transceiver User Guide. There is probably a clock cycle or two of uncertainty due to phase alignment of clocks and various settings. Simulate the MGT, and then monitor TXRUNDISP to see how many clock cycles later it asserts.