MAXSAVEDBLOCKS in netinet/tcp_sack.c

Matthew Dillon dillon at
Fri Aug 26 10:35:34 PDT 2005

:-On [20050826 14:46], Hiten Pandya (hmp at xxxxxxxxxxxxx) wrote:
:>Jeroen, that would be a good thing.  Given the complexity of the Selective 
:>Acknowledgement and its cousins, e.g. T-SACK, etc; it should definitely go 
:>into a separate manual page.
:Definitely.  SACK is a realm unto itself.  And to overload tcp(4) with it
:might be a bit overdone.  This way people looking for sack related stuff can
:immediately go to sack(4) and those who look for it in tcp(4) will find the
:reference easily.
:Jeroen Ruigrok van der Werven <asmodai(at)> / asmodai / kita no mono

    Urrm.  The SACK implementation is specific to the protocol.  The
    options should be left in tcp(4).  If someone wants to write a separate,
    more complete manual page just on SACK, then a sack(4) manual page is
    fine.  But basic documentation for the options belongs in tcp(4).

					Matthew Dillon 
					<dillon at xxxxxxxxxxxxx>

More information about the Kernel mailing list