From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) (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 7FC2E21F462 for ; Tue, 16 Jun 2015 09:33:49 -0700 (PDT) Received: by lbbwc1 with SMTP id wc1so14643762lbb.2 for ; Tue, 16 Jun 2015 09:33:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=6z9u+6K3mF3ay4LW6Ax9ecgXwJE1Lm4DjzZQBuoe+nA=; b=Culn1yP7gN/Asvay/Z3Cp40ywSv8jQqy5yB9ka3EAk6djztP1cNapQNvN2eIJiunED STobIcfhpeT+XpzL8D92yCypT1CTyRlbvEWDvOgn9t95yme6iQVYOqZnosc4A/T+7Vzs JRlsNF7TK1plNrRDXFR9FNG0yjZW/uCD1OXqbjm+o1uCvrvPSAcdW5EfLjB8eTs/hNaw TDEJlk33+c8pLsZwHZmQj+L/cqTpp7bfrSlZtgPJfzezelBwB+BHDok8/eAgq089c1bS PVHM9TI0V21OIaJNPR6s1R1XeLoNL1fgwwMItJjIHysb4YjxiCePSTV5pTLx1NeeZns7 s8iA== X-Received: by 10.112.119.198 with SMTP id kw6mr2165387lbb.97.1434472427734; Tue, 16 Jun 2015 09:33:47 -0700 (PDT) Received: from bass.home.chromatix.fi (87-93-133-238.bb.dnainternet.fi. [87.93.133.238]) by mx.google.com with ESMTPSA id k15sm345847laa.19.2015.06.16.09.33.45 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 16 Jun 2015 09:33:46 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Jonathan Morton In-Reply-To: <20150616161807.GA31289@sesse.net> Date: Tue, 16 Jun 2015 19:33:07 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <1A30B531-745C-4323-9929-9EEBD94D775F@gmail.com> References: <20150616161807.GA31289@sesse.net> To: "Steinar H. Gunderson" X-Mailer: Apple Mail (2.2098) Cc: bloat@lists.bufferbloat.net Subject: Re: [Bloat] using tcp_notsent_lowat in various apps? 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: Tue, 16 Jun 2015 16:34:19 -0000 > On 16 Jun, 2015, at 19:18, Steinar H. Gunderson = wrote: >=20 > On Tue, Jun 16, 2015 at 09:11:08AM -0700, Dave Taht wrote: >> I just tossed off a quick patch for rsync, not that I have a clue as >> to whether it would make any difference there. >=20 > For bulk applications (like rsync), how would this make sense at all? > I thought the entire point of this option was if you knew what data to = send > now, but that you might want to change your mind later if it takes = some time > to send it. The latter doesn't apply to rsync. Actually, it does. Rsync is designed to be used to update an existing = set of files, so the protocol interleaves control and data information = asynchronously. More generally, I think it=E2=80=99s worth setting LOWAT on *any* = application that uses select() or poll() with a readable and writable = socket population simultaneously. - Jonathan Morton