From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [PATCH] tcp: Socket option to set congestion window Date: Wed, 26 May 2010 19:33:46 +0200 Message-ID: <87fx1e1sat.fsf@basil.nowhere.org> References: <20100525220858.1071f238@nehalam> <20100525.225236.226781050.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: David Miller , shemminger@vyatta.com, netdev@vger.kernel.org, ycheng@google.com To: Tom Herbert Return-path: Received: from one.firstfloor.org ([213.235.205.2]:39022 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757234Ab0EZRdw (ORCPT ); Wed, 26 May 2010 13:33:52 -0400 In-Reply-To: (Tom Herbert's message of "Wed\, 26 May 2010 00\:06\:35 -0700") Sender: netdev-owner@vger.kernel.org List-ID: Tom Herbert writes: >> > Thanks to NAT, the concept of a network path or even host specific > path is a weakened concept.=A0 On the Internet this may be a path > characteristic per client, which unfortunately has no visibility in > the kernel other than per connection state.=A0 When a single IP addre= ss > may have thousands of hosts behind it, caching TCP parameters for tha= t > IP address is implicitly doing a huge aggregation-- probably dicey... Yes all of Saudi-Arabia used to be (is?) one IP address... Caching anything per IP is bogus. -Andi --=20 ak@linux.intel.com -- Speaking for myself only.