bsd/netinet/tcp_input.c

238         &tcp_autorcvbuf_inc_shift, 0, "Shift for increment in receive socket buffer size");
242         &tcp_autorcvbuf_max, 0, "Maximum receive socket buffer size");
263 /* This limit will determine when the receive socket buffer tuning will
424 	 * receive window to a minimum of MIN_IAJ_WIN packets
839 	/* The receive window scale negotiated at the
861  * This function is used to grow  a receive socket buffer. It
890 		 * the receive socket buffer needs to grow, increase
924 				 * Increment the receive window by a multiple of
927 				 * wire if it is limited by the receive window.
930 				 * measurements. We set the ideal size on receive
970 		/* How much can we trim the receive socket buffer?
1020  * Instead of enabling automatic receive socket buffer
1021  * resizing, just give more space to the receive socket buffer.
1223 		DTRACE_TCP5(receive, sruct mbuf *, m, struct inpcb *, NULL,
1316 	DTRACE_TCP5(receive, struct mbuf *, m, struct inpcb *, NULL,
1929  				 * not be able to receive options just after
2075 		TE_SENDECE will be cleared when we receive a packet with TH_CWR set.
2463 	 * Calculate amount of space in receive window,
2796 	 * receive window.  If segment begins before rcv_nxt,
2811 	 *   of our receive window, and we have to handle this case.
2822 	 * fit the receive window since RFC 1122 says:
2942 	 * this connection before trimming the data to fit the receive
3530 				 * If we can't receive any more
3624 		 * This is a kludge, but if we receive and accept
3675 		 * pull receive urgent pointer along
3676 		 * with the receive window.
4417 	 * Offer == -1 means that we didn't receive SYN yet,