From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) From: Anthony Sorace In-Reply-To: <418789bb5bc4501ab70366014c15b965@lilly.quanstro.net> Date: Fri, 21 Nov 2014 09:44:42 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <7f11f16bfdb01c0041b0397a1cea04c5@proxima.alt.za> <7dc7cfb35a012dedc41828d03d5cdff3@lilly.quanstro.net> <4CB999B4-E9C6-4A74-B849-4003DD3D23D1@9srv.net> <22d498b89c3b4d2e50c1c5cc0e9d72c0@lilly.quanstro.net> <536D0D14-3391-426A-930F-2B92FFD734DB@9srv.net> <418789bb5bc4501ab70366014c15b965@lilly.quanstro.net> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] running plan9 : an ideal setup? Topicbox-Message-UUID: 2dc07ab0-ead9-11e9-9d60-3106f5b1d025 On Nov 21, 2014, at 9:34 , erik quanstrom wrote: >=20 > this is not correct. tcp doesn't help at all when the wire is fast = (short, fat). it's the classic tradeoff of cpu > for (networking) performance. the wire being fast enough is an = argument against using tcp, > not for it. I don't think what we're saying is incompatible. I'm not saying that tcp = helps, or doesn't have overhead, with fast pipes. I'm saying that the = pipes are fast enough that in most use cases, at least for me, the pipe = is fast enough that ((wire speed) - (tcp/ip overhead)) is still plenty = fast.=