cnp3-ebook/protocols/tcp — English @ Weblate

Exit Zen

111 ../../protocols/tcp.rst:334 • ../../protocols/tcp.rst:347

	English 1 msec 6/10000 · 6
112 ../../protocols/tcp.rst:334

	English 524 Mbps 8/10000 · 8
113 ../../protocols/tcp.rst:335 • ../../protocols/tcp.rst:348

	English 10 msec 7/10000 · 7
114 ../../protocols/tcp.rst:335

	English 52.4 Mbps 9/10000 · 9
115 ../../protocols/tcp.rst:336 • ../../protocols/tcp.rst:349

	English 100 msec 8/10000 · 8
116 ../../protocols/tcp.rst:336

	English 5.24 Mbps 9/10000 · 9
117 ../../protocols/tcp.rst:337 • ../../protocols/tcp.rst:350

	English 500 msec 8/10000 · 8
118 ../../protocols/tcp.rst:337

	English 1.05 Mbps 9/10000 · 9
119 ../../protocols/tcp.rst:340

	English To solve this problem, a backward compatible extension that allows TCP to use larger receive windows was proposed in :rfc:`1323`. Today, most TCP implementations support this option. The basic idea is that instead of storing `snd.wnd` and `rcv.wnd` as 16 bits integers in the :term:`TCB`, they should be stored as 32 bits integers. As the TCP segment header only contains 16 bits to place the window field, it is impossible to copy the value of `snd.wnd` in each sent TCP segment. Instead the header contains `snd.wnd >> S` where `S` is the scaling factor ( :math:`0 \le S \le 14`) negotiated during connection establishment. The client adds its proposed scaling factor as a TCP option in the `SYN` segment. If the server supports :rfc:`1323`, it places in the `SYN+ACK` segment the scaling factor that it uses when advertising its own receive window. The local and remote scaling factors are included in the :term:`TCB`. If the server does not support :rfc:`1323`, it ignores the received option and no scaling is applied. 1023/10000 · 1023
120 ../../protocols/tcp.rst:342

	English By using the window scaling extensions defined in :rfc:`1323`, TCP implementations can use a receive buffer of up to 1 GByte. With such a receive buffer, the maximum throughput that can be achieved by a single TCP connection becomes : 234/10000 · 234
121 ../../protocols/tcp.rst:347

	English 8590 Gbps 9/10000 · 9
122 ../../protocols/tcp.rst:348

	English 859 Gbps 8/10000 · 8
123 ../../protocols/tcp.rst:349

	English 86 Gbps 7/10000 · 7
124 ../../protocols/tcp.rst:350

	English 17 Gbps 7/10000 · 7
125 ../../protocols/tcp.rst:357

	English These throughputs are acceptable in today's networks. However, there are already servers having 10 Gbps interfaces... Early TCP implementations had fixed receiving and sending buffers [#ftcphosts]_. Today's high performance implementations are able to automatically adjust the size of the sending and receiving buffer to better support high bandwidth flows [SMM1998]_. 368/10000 · 368
126 ../../protocols/tcp.rst:362

	English TCP's retransmission timeout 28/10000 · 28
127 ../../protocols/tcp.rst:364

	English In a go-back-n transport protocol such as TCP, the retransmission timeout must be correctly set in order to achieve good performance. On one hand, if the retransmission timeout expires too early, then bandwidth is wasted by retransmitting segments that have already been correctly received. On the other hand, if the retransmission timeout expires too late, then bandwidth is wasted because the sender is idle waiting for the expiration of its retransmission timeout. 467/10000 · 467
128 ../../protocols/tcp.rst:366

	English A good setting of the retransmission timeout clearly depends on an accurate estimation of the round-trip-time of each TCP connection. The round-trip-time differs between TCP connections, but may also change during the lifetime of a single connection. For example, the figure below shows the evolution of the round-trip-time between two hosts during a period of 45 seconds. 373/10000 · 373
129 ../../protocols/tcp.rst:372

	English Evolution of the round-trip-time between two hosts 50/10000 · 50
130 ../../protocols/tcp.rst:375

	English The easiest solution to measure the round-trip-time on a TCP connection is to measure the delay between the transmission of a data segment and the reception of a corresponding acknowledgment [#frttmes]_. As illustrated in the figure below, this measurement works well when there are no segment losses. 301/10000 · 301

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the previous translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.