DCCP socket option TX/RX info

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I am a master student in Montbéliard, France, and I do my internship
project on DCCP utilisation on linux.  I noticed two issues:

- RFC 3448 (3.2.2): "X_recev is the receiver estimate of sending rate
which is sent by the receiver to the sender"; x_recev matches the
value of tfrcrx_x_recv in the struct tfrc_rx_info, and the value of
tfrctx_x_recv in struct tfrc_rx_info, so the issue is that values of
(tfrctx_x_recv,tfrcrx_x_recv) are different, is it normal?

- if these values should be the same, why in the code source tfrc.h,
tfrcrx_x_recv is declared as _U32, and tfrctx_x_recv as _U64?

And a question:

- on the sender, is it possible that the application know about the
buffer length at the DCCP level (i.e. how many packets are awaiting to
be sent)?

Thank you,
--
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [IETF DCCP]     [Linux Networking]     [Git]     [Security]     [Linux Assembly]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]

  Powered by Linux