From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mike Haertel <mike@ducky.net>
Message-Id: <200111261929.fAQJT8f01844@ducky.net>
To: 9fans@cse.psu.edu
Subject: [9fans] having the Nagle cake and eating it too
Date: Mon, 26 Nov 2001 11:29:08 -0800
Topicbox-Message-UUID: 2a5455e0-eaca-11e9-9e20-41e7f4b1d025

The problem with Nagle seems to be that it clobbers performance
of RPC applications.  The communications pattern of such an
application is almost always:

	write(...request...);
	read(...response...);

(for clients) or

	write(...response...)
	read(...request...)

for servers.

Why not have read() force any outstanding writes to the network?
That way you could do the right thing even with programs whose
authors are too naive to know about turning off Nagle.