From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933092AbbDIRHL (ORCPT ); Thu, 9 Apr 2015 13:07:11 -0400 Received: from mail-ie0-f175.google.com ([209.85.223.175]:36328 "EHLO mail-ie0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753877AbbDIRHI (ORCPT ); Thu, 9 Apr 2015 13:07:08 -0400 Message-ID: <1428599225.25985.267.camel@edumazet-glaptop2.roam.corp.google.com> Subject: Re: "tcp: refine TSO autosizing" causes performance regression on Xen From: Eric Dumazet To: Stefano Stabellini Cc: xen-devel@lists.xensource.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, christoffer.dall@linaro.org, Ian Campbell , Wei Liu , David Vrabel , edumazet@google.com, Konrad Rzeszutek Wilk , netdev Date: Thu, 09 Apr 2015 10:07:05 -0700 In-Reply-To: References: <1428596218.25985.263.camel@edumazet-glaptop2.roam.corp.google.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2015-04-09 at 17:36 +0100, Stefano Stabellini wrote: > A very big difference: > > echo 262144 > /proc/sys/net/ipv4/tcp_limit_output_bytes > brings us much closer to the original performance, the slowdown is just > 8% Cool. > > echo 1048576 > /proc/sys/net/ipv4/tcp_limit_output_bytes > fills the gap entirely, same performance as before "refine TSO > autosizing" Sure, this basically disables TCP Small Queue and select the opposite : Favor single flow throughput and huge latencies (bufferbloat) > > > What would be the next step for here? Should I just document this as an > important performance tweaking step for Xen, or is there something else > we can do? I guess this is a reasonable choice. Note that /proc/sys/net/ipv4/tcp_limit_output_bytes is already documented.