Return-path: Received: from g9t1613g.houston.hp.com ([15.240.0.71]:39926 "EHLO g9t1613g.houston.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752809AbbBFRsX (ORCPT ); Fri, 6 Feb 2015 12:48:23 -0500 Received: from g2t2353.austin.hp.com (g2t2353.austin.hp.com [15.217.128.52]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by g9t1613g.houston.hp.com (Postfix) with ESMTPS id 8AC3E690B2 for ; Fri, 6 Feb 2015 17:48:22 +0000 (UTC) Message-ID: <54D4FE63.9020602@hp.com> (sfid-20150206_185023_913393_9A770373) Date: Fri, 06 Feb 2015 09:48:19 -0800 From: Rick Jones MIME-Version: 1.0 To: Eric Dumazet , Michal Kazior CC: Neal Cardwell , linux-wireless , Network Development , Eyal Perry Subject: Re: Throughput regression with `tcp: refine TSO autosizing` References: <1423055810.907.125.camel@edumazet-glaptop2.roam.corp.google.com> <1423056591.907.130.camel@edumazet-glaptop2.roam.corp.google.com> <1423084303.31870.15.camel@edumazet-glaptop2.roam.corp.google.com> <1423141038.31870.38.camel@edumazet-glaptop2.roam.corp.google.com> <1423142342.31870.49.camel@edumazet-glaptop2.roam.corp.google.com> <1423147286.31870.59.camel@edumazet-glaptop2.roam.corp.google.com> <1423156205.31870.86.camel@edumazet-glaptop2.roam.corp.google.com> <1423230001.31870.128.camel@edumazet-glaptop2.roam.corp.google.com> <1423233346.31870.136.camel@edumazet-glaptop2.roam.corp.google.com> In-Reply-To: <1423233346.31870.136.camel@edumazet-glaptop2.roam.corp.google.com> Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: > If you increase ability to flood on one flow, then you need to make sure > receiver has big rcvbuf as well. > > echo 2000000 >/proc/sys/net/core/rmem_default > > Otherwise it might drop bursts. > > This is the kind of things that TCP does automatically, not UDP. An alternative, if the application involved can make explicit setsockopt() calls to set SO_SNDBUF and/or SO_RCVBUF, is to tweak rmem_max and wmem_max and then let the application make the setsockopt() calls. Which path one would take would depend on circumstances I suspect. rick jones