Home
last modified time | relevance | path

Searched refs:MSS (Results 1 – 11 of 11) sorted by relevance

/external/netperf/doc/examples/
Dpacket_byte_script70 MSS=`$NETPERF_CMD -H $REM_HOST -t TCP_MSS -P 0 -v 0`
78 while [ $bar -lt $MSS ]
87 bar=`expr $MSS \* $i`
93 while [ $bar -lt $MSS ]
101 bar=`expr $MSS \* $i`
/external/iptables/extensions/
Dlibxt_tcpmss.man1 … matches the TCP MSS (maximum segment size) field of the TCP header. You can only use this on TCP…
4 Match a given TCP MSS value or range.
Dlibxt_TCPMSS.man1 This target allows to alter the MSS value of TCP SYN packets, to control
28 Explicitly sets MSS option to specified value. If the MSS of the packet is
30 2.6.25 onwards) to avoid more problems with hosts relying on a proper MSS.
33 Automatically clamp MSS value to (path_MTU \- 40 for IPv4; \-60 for IPv6).
Dlibxt_osf.man2 compares some data (Window Size, MSS, options and their order, TTL, DF,
/external/iptables/utils/
Dpf.os37 # systems, it is a multiple of MSS or MTU (MSS+40). In some rare
41 # appears to be a multiple of MSS (MSS*nn); a special value of 'Tnn'
42 # means it is a multiple of MTU ((MSS+40)*nn). Unless you notice the
45 # MTU, you can however multiply S value by MSS, or T value by MSS+40,
75 # - Maximum segment size (MSS) - this setting is usually link-dependent. P0f
81 # is using a value it pulled out of nowhere. Specific unique MSS
98 # - The sequence of TCP all options (MSS, window scaling, selective ACK
115 # "S" and "T" which are a multiple of MSS or a multiple of MTU
244 # is selected as a multiple of MTU instead of MSS. I got
368 # awkward MSS of 536, which I use to tell one from another
[all …]
/external/mesa3d/src/mesa/x86/
Dmmx_blend.S240 #define GMB_STORE(rgba, MSS ) \ argument
241 ONE(MOVD ( MSS, REGIND(rgba) )) /* | | | | sa1 | sb1 | sg1 | sr1 */ ;\
242 TWO(MOVQ ( MSS, REGIND(rgba) )) /* sa2 | sb2 | sg2 | sr2 | sa1 | sb1 | sg1 | sr1 */
/external/netperf/
DREADME.hpux25 happen to send sub-MSS requests and/or responses you _cannot_ assume
DRelease_Notes307 *) A TCP_MSS test has been added which will report the MSS for a data
311 This means that if the MSS is one which might change over the life
317 to parameterize things based on the MSS - for example the
/external/netperf/doc/
Dnetperf.info1481 a nutshell it forces sub-MSS sends to be buffered so every segment
1482 sent is Maximum Segment Size (MSS) unless the application performs
1486 size" (`-m' option) is smaller than the MSS. It should also
1499 when the send size (`-m' option) is larger than the MSS or will
1501 send size is smaller than the MSS. This stems from TCP_NODELAY
1502 causing each sub-MSS send to be its own TCP segment rather than
1508 demand for tests where the send size (`-m') is larger than the MSS
2602 it compared with the "MSS" for the connection.
3501 This will display the Maximum Segment Size (aka MSS) or its
3503 of -1 means either the concept of an MSS did not apply to the
Dnetperf.texi1592 nutshell it forces sub-MSS sends to be buffered so every segment sent
1593 is Maximum Segment Size (MSS) unless the application performs an
1597 (@option{-m} option) is smaller than the MSS. It should also improve
1610 (@option{-m} option) is larger than the MSS or will decrease reported
1612 the MSS. This stems from TCP_NODELAY causing each sub-MSS send to be
1619 than the MSS it suggests the TCP/IP stack's implementation of the
2746 it compared with the @dfn{MSS} for the connection.
3606 This will display the Maximum Segment Size (aka MSS) or its equivalent
3608 either the concept of an MSS did not apply to the protocol being used,
/external/iproute2/doc/
Dip-cref.tex1348 --- \threeonly the MSS (``Maximal Segment Size'') to advertise to these
1371 MSS (``Maximal Segment Size'') for same connection. The default is
1378 + by the MSS (''Maximal Segment Size'') of the connection. The default