From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) (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 6C9A921F4F5; Tue, 16 Jun 2015 09:11:09 -0700 (PDT) Received: by obbgp2 with SMTP id gp2so14729902obb.2; Tue, 16 Jun 2015 09:11:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=U7PsovXxtGzVk/GUxNmS1AbATCf6rxoThvNlG1XkeVM=; b=FJmy7Rbta/iHCAf5lW2oL35Y3e0VplD89WdobNx7oZL+HfJqA+ccXUtGbbiA7mkUkn 0Wx/7Pn956w9whwdAX5pEPhkiyJXdOwD6Tuio+zBksKxukOGNkT4ua7tQUua32LPMUem 2aZpmPeL0lSNd+KxlfVxp8/0+DDI7qR4hk/hVEZy8rc4WGVrwGPVhtHIjlLOBCzx8IeE 9+2dshFmb8my8oIacYCVlgBLcCXvi7PyF4/FsdrpNVWfMABCk5+CbadeNwrM1Dhrtj0A myu0gA9cl34rjiTVxhG2Ea+h2JlA/cW7SyDvnM88n5BPhpVgKnWFNf6ygD/ifusA8B9P fr4g== MIME-Version: 1.0 X-Received: by 10.60.178.33 with SMTP id cv1mr894986oec.11.1434471069107; Tue, 16 Jun 2015 09:11:09 -0700 (PDT) Received: by 10.202.105.129 with HTTP; Tue, 16 Jun 2015 09:11:08 -0700 (PDT) Date: Tue, 16 Jun 2015 09:11:08 -0700 Message-ID: Subject: using tcp_notsent_lowat in various apps? From: Dave Taht To: bloat-devel , bloat Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: bloat-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Developers working on AQM, device drivers, and networking stacks" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jun 2015 16:11:38 -0000 In light of apple's: https://developer.apple.com/videos/wwdc/2015/?id=3D719 I am curious if anyone has tried this new socket option in appropriate apps= , (web browsers, screen sharers like tightvnc, X11, etc)? Would it be helpful in openssh/dropbear? What other sorts of apps? It looks like using it in chrome got stuck on battery life analsysis: https://code.google.com/p/chromium/issues/detail?id=3D310927 It does not appear to be a define in my fairly recently version of gcc, and looking at the kernel for linux it looks like "25" is correct there. it is defined to be 0x201 in OSX/ios: http://fxr.watson.org/fxr/source/bsd/netinet/tcp.h?v=3Dxnu-2050.18.24#L217 (and now on universally in dev builds of ios) I just tossed off a quick patch for rsync, not that I have a clue as to whether it would make any difference there. diff --git a/socket.c b/socket.c index 3f5786b..bbb2461 100644 --- a/socket.c +++ b/socket.c @@ -406,6 +406,8 @@ static int *open_socket_in(int type, int port, const char *bind_addr, int af_hint) { int one =3D 1; + const int lowat =3D 16 * 1024; + int rc; int s, *socks, maxs, i, ecnt; struct addrinfo hints, *all_ai, *resp; char portbuf[10], **errmsgs; @@ -451,6 +453,12 @@ static int *open_socket_in(int type, int port, const char *bind_addr, setsockopt(s, SOL_SOCKET, SO_REUSEADDR, (char *)&one, sizeof one); +#ifndef TCP_NOTSENT_LOWAT +#define TCP_NOTSENT_LOWAT 25 +#endif + rc =3D setsockopt(s, IPPROTO_TCP, TCP_NOTSENT_LOWAT, + (char *)&lowat, sizeof lowat); + if(rc !=3D 0) { perror("lowatfailed"); } if (sockopts) set_socket_options(s, sockopts); else --=20 Dave T=C3=A4ht What will it take to vastly improve wifi for everyone? https://plus.google.com/u/0/explore/makewififast