Trivial spelling corrections in comments; update some comments in a Kconfig file.

This commit is contained in:
Gregory Nutt 2018-06-24 15:01:49 -06:00
parent 0786b5d053
commit 715d561c41
4 changed files with 10 additions and 5 deletions

View File

@ -72,6 +72,11 @@ config NET_ETH_TCP_RECVWNDO
buffering via IOBs. To include IOB aware windowing logic also buffering via IOBs. To include IOB aware windowing logic also
enable CONFIG_NET_TCP_RWND_CONTROL. enable CONFIG_NET_TCP_RWND_CONTROL.
The default values correspond to the MSS associated with the
minimum MSS: IPv4 hosts are required to be able to handle an MSS
of at least 536 octets; IPv6 hosts are required to be able to handle
an MSS of 1220 octets.
config NET_SLIP_MTU config NET_SLIP_MTU
int # "SLIP packet buffer size (MTU)" int # "SLIP packet buffer size (MTU)"
default 296 default 296
@ -83,7 +88,7 @@ config NET_SLIP_MTU
This value is normally referred to as the MTU (Maximum Transmission Unit); This value is normally referred to as the MTU (Maximum Transmission Unit);
the payload payload is the MSS (Maximum Segment Size). the payload payload is the MSS (Maximum Segment Size).
SLIP is required to support at lest 256+20+20 = 296. Values other than SLIP is required to support at least 256+20+20 = 296. Values other than
296 are not recommended. 296 are not recommended.
The Linux slip module hard-codes its MTU size to 296 (40 bytes for The Linux slip module hard-codes its MTU size to 296 (40 bytes for

View File

@ -121,7 +121,7 @@
* IPv4_REASS_BUFSIZE. * IPv4_REASS_BUFSIZE.
* 3. Since there is only a single reassembly buffer, IPv4 reassembly cannot * 3. Since there is only a single reassembly buffer, IPv4 reassembly cannot
* be used in a context where multiple network devices may be concurrently * be used in a context where multiple network devices may be concurrently
* re-assemblying packets. * re-assembling packets.
*/ */
#define IP_MF 0x20 /* See IP_FLAG_MOREFRAGS */ #define IP_MF 0x20 /* See IP_FLAG_MOREFRAGS */
@ -228,7 +228,7 @@ static uint8_t devif_reassembly(FAR struct net_driver_s *dev)
else else
{ {
/* If the two endpoints are in different bytes, we update the bytes /* If the two endpoints are in different bytes, we update the bytes
* in the endpoints and fill the stuff inbetween with 0xff. * in the endpoints and fill the stuff in between with 0xff.
*/ */
g_reassembly_bitmap[offset / (8 * 8)] |= g_reassembly_bitmap[offset / (8 * 8)] |=

View File

@ -114,7 +114,7 @@ static void tcp_input(FAR struct net_driver_s *dev, uint8_t domain,
/* Get the size of the IP header and the TCP header. /* Get the size of the IP header and the TCP header.
* *
* REVISIT: TCP header is *not* a constant! It can be larger if the * REVISIT: TCP header is *not* a constant! It can be larger if the
* TCP header includes options. The constand TCP_HDRLEN should be * TCP header includes options. The constant TCP_HDRLEN should be
* replaced with the macro TCP_OPT_HDRLEN(n) which will calculate the * replaced with the macro TCP_OPT_HDRLEN(n) which will calculate the
* correct header length in all cases. * correct header length in all cases.
*/ */

View File

@ -376,7 +376,7 @@ static void tcp_sendcommon(FAR struct net_driver_s *dev,
* link-layer, IP, and TCP headers. This logic here assumes that * link-layer, IP, and TCP headers. This logic here assumes that
* all IOBs are available for TCP buffering. * all IOBs are available for TCP buffering.
* *
* REVISIT: In an environment with mutliple, active read-ahead TCP * REVISIT: In an environment with multiple, active read-ahead TCP
* sockets (and perhaps multiple network devices) or if there are * sockets (and perhaps multiple network devices) or if there are
* other consumers of IOBs (such as for TCP write buffering) then the * other consumers of IOBs (such as for TCP write buffering) then the
* total number of IOBs will all not be available for read-ahead * total number of IOBs will all not be available for read-ahead