From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 639753B29D for ; Fri, 24 Jan 2020 16:25:10 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1579901109; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=dLQ8zqNPARFXXzwyr/WfknDP4XaHK49q/KPuS1cb0V4=; b=O46dhhnwexrAHnAuP1Cdw1WdSmfPC6JrFhDFinEIIUU/8Lxfoyvd6hy2Ak2sjdrYxBKeoD J6+/5OOHK4B3AWDA0Wt1r2xjqWmXiX4FQF0igbakYVizslrDCcy4W6E+fQK0MYCmYQv0Wu HAO3yOuI+kTNZujCdHPWKTwTvaj+kI4= Received: from mail-lj1-f197.google.com (mail-lj1-f197.google.com [209.85.208.197]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-412-bxf_uw07O2izFS-oZaE76A-1; Fri, 24 Jan 2020 16:25:07 -0500 Received: by mail-lj1-f197.google.com with SMTP id s25so892704ljm.9 for ; Fri, 24 Jan 2020 13:25:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:in-reply-to:references:date :message-id:mime-version; bh=1/2aYHPCUCzuG7cyZlcTwNC/itZlz3AG95knybCra8M=; b=uA3fv33CQT7OLUNzke0Iq8mRpxNof5YxzGGS3aDz05xR9Es6NQVYtZAo6whNGtqlnG bo3H5l4ckiOOzoqHFi/Scs8Qg15C30jH0MTd/MQxJlNXIEVdcVoxRNlZvRlBHS6p+F7F qKGUfYFAK33r8P++QRladHGDsd8pGGgWmttK+vO6GGK3GjY5qPBMCC9iSol4ICVY6CTe u7itljLPiC/13LLclOKpPXpAgFt+AVHk5B5yigmwzp6HtmHAFqo2BLtCeDzLuyo4S2+I pvnl4WVzCS7ERa7bXoO3fRs3/U9VMgk4/NX4apc6Mbyzh7567Z0XE4QRLlNO0nWpS7HS sO0A== X-Gm-Message-State: APjAAAVc7GJHdTtdKyHpYxiNTK32SvBDK1WwhvnP4lZNsGVvuRbPseT+ m2wrG73PNVXz3FibeRPQYSxE5C0JhCeQwJtjhjx69RO32xS/mg1x1nc69SDX61Oz88Vj2jWOswr iEXRC9JRUtAuBfU9eKIrLg5mp/+UtnsbY27g= X-Received: by 2002:a2e:858b:: with SMTP id b11mr3551841lji.135.1579901105993; Fri, 24 Jan 2020 13:25:05 -0800 (PST) X-Google-Smtp-Source: APXvYqwbgv1bBflMbMclPyBVH/JDncY271HDu5LdBfqpkxoPM9FpWFUtag9zfx1OLfpTKsCwttvCVg== X-Received: by 2002:a2e:858b:: with SMTP id b11mr3551830lji.135.1579901105753; Fri, 24 Jan 2020 13:25:05 -0800 (PST) Received: from alrua-x1.borgediget.toke.dk ([2a0c:4d80:42:443::2]) by smtp.gmail.com with ESMTPSA id h14sm3508142lfc.2.2020.01.24.13.25.04 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 24 Jan 2020 13:25:05 -0800 (PST) Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id 34BAA180073; Fri, 24 Jan 2020 22:25:03 +0100 (CET) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= To: Bob McMahon , Make-Wifi-fast In-Reply-To: References: X-Clacks-Overhead: GNU Terry Pratchett Date: Fri, 24 Jan 2020 22:25:03 +0100 Message-ID: <87d0b8fsy8.fsf@toke.dk> MIME-Version: 1.0 X-MC-Unique: bxf_uw07O2izFS-oZaE76A-1 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Subject: Re: [Make-wifi-fast] iperf 2.0.14 X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jan 2020 21:25:10 -0000 Bob McMahon via Make-wifi-fast writes: > From: Bob McMahon > Subject: iperf 2.0.14 > To: Make-Wifi-fast > Date: Fri, 24 Jan 2020 12:52:16 -0800 > > Hi All, > > Just a heads up that iperf 2.0.14 > is getting closer to a release. Feel free to suggest features that you > might find helpful. I have an old TODO item sitting around telling me to go over which features we use from netperf in Flent that we don't currently use for iperf. So thank you for the reminder; since I'm leaving for holidays tomorrow, here is a quick overview (i.e., I haven't had time to go over how many of these are actually missing from iperf, and how many are there, but we're just not using them): - We extract the following variables from netperf (-k option): output_vars =3D 'THROUGHPUT,LOCAL_CONG_CONTROL,REMOTE_CONG_CONTROL,' \ 'TRANSPORT_MSS,LOCAL_TRANSPORT_RETRANS,' \ 'REMOTE_TRANSPORT_RETRANS,LOCAL_SOCKET_TOS,' \ 'REMOTE_SOCKET_TOS,DIRECTION,ELAPSED_TIME,PROTOCOL,' \ 'LOCAL_SEND_SIZE,LOCAL_RECV_SIZE,' \ 'REMOTE_SEND_SIZE,REMOTE_RECV_SIZE,' \ 'LOCAL_BYTES_SENT,LOCAL_BYTES_RECVD,' \ 'REMOTE_BYTES_SENT,REMOTE_BYTES_RECVD' - We pass in DUMP_TCP_INFO to netperf and capture the output (ref: https://github.com/tohojo/flent/issues/13) - We use the netperf features to set: - diffserv markings - TCP congestion control - socket timeout - For running the public test servers, the ability to just leave a 'netserver' instance running indefinitely and let it take care of negotiating test setups. I don't think this works that well with iperf? If iperf can replicate all of that, it'll be fairly straight-forward to make Flent backend-agnostic on the TCP test runner front. How much do you reckon is currently missing, and what would it take to get that in? :) -Toke