From owner-freebsd-net Wed Jan 13 11:46:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13328 for freebsd-net-outgoing; Wed, 13 Jan 1999 11:46:39 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13316 for ; Wed, 13 Jan 1999 11:46:36 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id KAA21921; Wed, 13 Jan 1999 10:25:16 -0500 (EST) (envelope-from wollman) Date: Wed, 13 Jan 1999 10:25:16 -0500 (EST) From: Garrett Wollman Message-Id: <199901131525.KAA21921@khavrinen.lcs.mit.edu> To: yu.shi@research.nokia.com Cc: net@FreeBSD.ORG Subject: piggy-backed ACKs In-Reply-To: <369C4A50.8EA01BB5@research.nokia.com> References: <369C4A50.8EA01BB5@research.nokia.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > In a TCP connection, who decides that ACKs are piggy-backed or not. The TCP stack will always try to send data when it sends an ack if there is data to be sent and the flow-control algorithms would permit data to be sent. > IF I implement an application, can I make ACKs not piggy-backed? Only if you rewrite the TCP stack. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message