Date: Mon, 7 Mar 2005 11:39:46 -0500 (EST) From: c0ldbyte <c0ldbyte@myrealbox.com> To: Noritoshi Demizu <demizu@dd.iij4u.or.jp> Cc: freebsd-net@freebsd.org Subject: Re: Why TCP_MAX_SACK == 3 ? Message-ID: <20050307113917.V15707@eleanor.us1.wmi.uvac.net> In-Reply-To: <20050308.001714.41652371.Noritoshi@Demizu.ORG> References: <20050308.001714.41652371.Noritoshi@Demizu.ORG>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 8 Mar 2005, Noritoshi Demizu wrote: > In netinet/tcp.h, TCP_MAX_SACK is defined as follows. > > #define TCP_MAX_SACK 3 /* MAX # SACKs sent in any segment */ > > Shouldn't it be 4? If a peer node does not use TCP timestamps option, > four SACK blocks can be sent. For example, if my memory serves correctly, > Microsoft Windows does not use TCP timestamps option by default. > > > By the way, currently, both window scale option and timestamps option > are controled by one sysctl variable: net.inet.tcp.rfc1323. > Wouldn't it be nice if each option had its own sysctl variable? > > Regards, > Noritoshi Demizu As Im showing in my source tree for 4.11 \ #define TCPOPT_SACK_PERMITTED 4 /* Experimental */ #define TCPOLEN_SACK_PERMITTED 2 #define TCPOPT_SACK 5 /* Experimental */ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) Comment: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xF7DF979F iD8DBQFCLIPVsmFQuvffl58RAg6ZAJ93OjZxUnjzmzVDFCsYV6vF1VSRbwCcDeTL 0Lk/WpovPFMPV9c3thb/FPY= =wKZs -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050307113917.V15707>