Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932871AbbDIQRE (ORCPT ); Thu, 9 Apr 2015 12:17:04 -0400 Received: from mail-ig0-f170.google.com ([209.85.213.170]:37594 "EHLO mail-ig0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753716AbbDIQRB (ORCPT ); Thu, 9 Apr 2015 12:17:01 -0400 Message-ID: <1428596218.25985.263.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 09:16:58 -0700 In-Reply-To: References: 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 Content-Length: 1496 Lines: 46 On Thu, 2015-04-09 at 16:46 +0100, Stefano Stabellini wrote: > Hi all, > > I found a performance regression when running netperf -t TCP_MAERTS from > an external host to a Xen VM on ARM64: v3.19 and v4.0-rc4 running in the > virtual machine are 30% slower than v3.18. > > Through bisection I found that the perf regression is caused by the > prensence of the following commit in the guest kernel: > > > commit 605ad7f184b60cfaacbc038aa6c55ee68dee3c89 > Author: Eric Dumazet > Date: Sun Dec 7 12:22:18 2014 -0800 > > tcp: refine TSO autosizing > > > A simple revert would fix the issue. > > Does anybody have any ideas on what could be the cause of the problem? > Suggestions on what to do to fix it? You sent this to lkml while networking discussions are on netdev. This topic had been discussed on netdev multiple times. This commit restored original TCP Small Queue behavior, which is the first step to fight bufferbloat. Some network drivers are known to be problematic because of a delayed TX completion. So far this commit did not impact max single flow throughput on 40Gb mlx4 NIC. (ie : line rate is possible) Try to tweak /proc/sys/net/ipv4/tcp_limit_output_bytes to see if it makes a difference ? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/