From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-x22b.google.com (mail-pb0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 109582021A8 for ; Fri, 21 Mar 2014 08:06:22 -0700 (PDT) Received: by mail-pb0-f43.google.com with SMTP id um1so2513467pbc.16 for ; Fri, 21 Mar 2014 08:06:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:to:cc:date:in-reply-to:references :content-type:content-transfer-encoding:mime-version; bh=Nv1MfNjwBbyYKjyjKGO8Pho+oo+z1xkEc7pMA4oNm7k=; b=dB1H4VbpDRlDHkkTU1YzvWl40SG0EWEJC727fAeLpcA7nz6bMh2p7yOL28b5W7lRx9 Oqcr3CWO185BK3eRebb6FJVe/S3qRdzDr2PWAG7mmDN844N0jjYg5RklEm7jBEY6bQfn 3YwxbIdpiEmXHggzDsE1bmj94A/tpBrbhPjfi1sSefGONTVgeD7FX4RXQhg+n54F+GZz DrX8PVKxH9tL2u+/NK4hBMWzNCxo7BXtE9ScNjPEZ5u43j1j97qk03KAtNvUxU1YZZNQ sVA47RHY069EHKAPI7usBluS14ZYgngLbrm2TkZzAKxVJBr5hSaE0cvVXxLjttaTQS3a 1npw== X-Received: by 10.66.141.165 with SMTP id rp5mr54937888pab.90.1395414381344; Fri, 21 Mar 2014 08:06:21 -0700 (PDT) Received: from [172.19.250.111] ([172.19.250.111]) by mx.google.com with ESMTPSA id pq3sm10387980pbb.57.2014.03.21.08.06.20 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Fri, 21 Mar 2014 08:06:20 -0700 (PDT) Message-ID: <1395414379.6441.17.camel@edumazet-glaptop2.roam.corp.google.com> From: Eric Dumazet To: renaud sallantin Date: Fri, 21 Mar 2014 08:06:19 -0700 In-Reply-To: References: <20140318145221.GA31327@sesse.net> <07BD4518-2A7E-4F43-8978-791E3B2BDA2A@cisco.com> <87eh1wc05c.fsf@toke.dk> <87a9ckbz1q.fsf@toke.dk> <1395358884.9114.102.camel@edumazet-glaptop2.roam.corp.google.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Cc: "Steinar H. Gunderson" , bloat Subject: Re: [Bloat] AQM creeping into L2 equipment X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Mar 2014 15:06:22 -0000 On Fri, 2014-03-21 at 09:15 +0100, renaud sallantin wrote: > > FQ/pacing enables to do a lot of things, > and as I already said, it could be used to easily implement the > Initial Spreading. > (we did it and it' s just a few lines to add, and a couple of > parameters to change) > > > But for the moment, FQ/Pacing sends the IW in one burst (up to 10 > segments). > This is not true. This depends on RTT and your qdisc parameters. Whole point of TSO autosizing is to make all this stuff automatic. Here is the tcpdump output for a 10ms RTT, which is quite standard. You can see 5 packets are sent, with a delay of more than 1 ms. 07:58:52.616379 IP 10.246.11.51.39905 > 10.246.11.52.41276: S 2187811646:2187811646(0) win 29200 07:58:52.626575 IP 10.246.11.52.41276 > 10.246.11.51.39905: S 81785763:81785763(0) ack 2187811647 win 29200 07:58:52.626642 IP 10.246.11.51.39905 > 10.246.11.52.41276: . ack 1 win 457 07:58:52.626671 IP 10.246.11.51.39905 > 10.246.11.52.41276: . 1:2921(2920) ack 1 win 457 07:58:52.627740 IP 10.246.11.51.39905 > 10.246.11.52.41276: . 2921:5841(2920) ack 1 win 457 07:58:52.628815 IP 10.246.11.51.39905 > 10.246.11.52.41276: . 5841:8761(2920) ack 1 win 457 07:58:52.629946 IP 10.246.11.51.39905 > 10.246.11.52.41276: . 8761:11681(2920) ack 1 win 457 07:58:52.631054 IP 10.246.11.51.39905 > 10.246.11.52.41276: . 11681:14601(2920) ack 1 win 457 07:58:52.637147 IP 10.246.11.52.41276 > 10.246.11.51.39905: . ack 2921 win 274 07:58:52.637207 IP 10.246.11.51.39905 > 10.246.11.52.41276: . 14601:17521(2920) ack 1 win 457 07:58:52.638117 IP 10.246.11.51.39905 > 10.246.11.52.41276: . 17521:20441(2920) ack 1 win 457 07:58:52.638114 IP 10.246.11.52.41276 > 10.246.11.51.39905: . ack 5841 win 320 07:58:52.639011 IP 10.246.11.51.39905 > 10.246.11.52.41276: . 20441:23361(2920) ack 1 win 457 You also can tune /proc/sys/net/ipv4/tcp_min_tso_segs from 2 to 1 if you really want... No kernel patches needed...