Re: [PATCH 1/1] DCCP: Fix up t_nom - FOLLOW-UP

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

 



|  > I have a snapshot which illustrates this state:
|  >
|  >  http://www.erg.abdn.ac.uk/users/gerrit/dccp/dccp_probe/examples/no_tx_locking/transmit_rate.png
|  >
|  > The oscillating behaviour is well visible. In contrast, I am sure that you would agree that the
|  > desirable state is the following:
|  >
|  >  http://www.erg.abdn.ac.uk/users/gerrit/dccp/dccp_probe/examples/with_tx_locking/transmit_rate.png
|  >
|  
|  Questions on the graphs:
|  - are these direct connect nodes?
The nodes are on the same Ethernet LAN, connected via 100Mbps / 1GBps interfaces. There is no
other traffic on that LAN.
|  - why is Xcalc 0?
Since no losses occurred (p is always 0 on these tests).
|  - why on the stable one is Xrecv different from X. Is X the rate that
|  it is allowed to send at but doesn't so only achieves Xrecv?
When there is no loss, X = max(min(2*X, 2*X_recv), s/R) - the graph agrees with this, since
X is about 2*X_recv.
-
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