From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id A41ED3CB3A for ; Thu, 18 Jul 2019 16:28:11 -0400 (EDT) Received: by mail-wm1-x330.google.com with SMTP id a15so26768060wmj.5 for ; Thu, 18 Jul 2019 13:28:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EHNQYbcKg7CcXdfrsvg2wL9oJgwkNk4dVghAFmlU4Eg=; b=S3HtGgDlTT46ZN51oy74UPE0YUWpk/sJP5RTWETe7FWd/bh994rUOK0FUXcaUXS0W5 8fAHY5r8QpWw6NZ78rDZjaZBKW37PI3Fobk7uaMMMJZmEgUhbnScmQP2p1Arh9joVy9d aRu5I8mVqBjMQQ9mrCZOYKN1oFxf+PamuKlcc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=EHNQYbcKg7CcXdfrsvg2wL9oJgwkNk4dVghAFmlU4Eg=; b=PqLCL82m4DxS6BuKFTTYt2idp6q7qNGuu+o3/YasSWFcspZf6qZ4cPPCAHfu8rpEYg lu9ZJILECntjZpmCJatE82TwfDUYnSbLKNFvkNtUgu28ReoTHZwDpHS2lQTO2ey9lwLZ 1VLY3bysIgM/lORpxceaAxWljF7lQsxWsa5sb+gk+zAnpymRvR2uAPnYiqqcDDIY3RCI fdOnKTmFofIo4G9IM37h72fHrCsroLGZ6kSUAwYTY4zaA/QJGT24bG2SPHjg1UxWInDs Ec/cp1maNz/BvEH/QVecdTc/tK5os2H/DkAP4sZWUbSkl4nUtHZX5bECxoE/NYy3eVU1 nXTg== X-Gm-Message-State: APjAAAX0ijpRIUH/ZQqWtDb+aI17/RNSn3p+4WRS30YEw2HyVZH8EEd+ fODeXRcI4ts+h6sYDfJgkNuCj63CfW5RM94woCfXZQ== X-Google-Smtp-Source: APXvYqw5lddvUJiDaIqEhSoJ7UPKBcX/F8xfvEi0qhpNiW+MwqCCAYPexDm1Q2caUEaexCjdUXPS2bLZStidSJCI1uw= X-Received: by 2002:a1c:1f4e:: with SMTP id f75mr42749165wmf.137.1563481690585; Thu, 18 Jul 2019 13:28:10 -0700 (PDT) MIME-Version: 1.0 References: <874l3k70wi.fsf@toke.dk> In-Reply-To: <874l3k70wi.fsf@toke.dk> From: Bob McMahon Date: Thu, 18 Jul 2019 13:27:58 -0700 Message-ID: To: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= Cc: Make-Wifi-fast Content-Type: multipart/alternative; boundary="000000000000c7ff66058dfa72d7" Subject: Re: [Make-wifi-fast] Fwd: iperf 2 "short term" road map 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: Thu, 18 Jul 2019 20:28:11 -0000 --000000000000c7ff66058dfa72d7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Toke, Do let me know. We're focused on the network i/o testing aspect (per being a WiFi chip vendor) and are intentionally not trying to provide CPU load metrics. (I think netperf provides both.) A feature we are adding is to warn when we think something other than the socket reads() and writes() have become bottlenecks, e.g. in a CPU constrained system it becomes an "entangled metric" between i/o and CPU though still presents in network i/o units which can be misleading to network device vendors. Also, many might want to consider monitoring "network power" which is average throughput / latency or delay, i.e. "something good" / "something bad" Bob On Wed, Jul 17, 2019 at 3:26 PM Toke H=C3=B8iland-J=C3=B8rgensen wrote: > Bob McMahon writes: > > > Just an FYI in case anybody has interest in traffic tooling. > > I do! Specifically, I am planning to teach Flent to automatically switch > between iperf and netperf as the underlying test tool[0]. I believe that > there are a few netperf features missing from iperf that Flent currently > uses, so I'll get back to you with actual feature requests for those > once I've had a chance to take a look at this in more detail :) > > -Toke > > [0] The main driver for this is netperf's weird license which makes it > impossible to package for FOSS-only distributions; leading to things > like this: https://bugzilla.redhat.com/show_bug.cgi?id=3D1729939 > --000000000000c7ff66058dfa72d7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Toke,

Do let me know.=C2=A0 We're focused o= n the network i/o testing aspect (per being a WiFi chip vendor) and are int= entionally not trying to provide CPU load metrics. (I think netperf provide= s both.)=C2=A0 A feature we are adding is to warn when we think something o= ther than the socket reads() and writes() have become bottlenecks, e.g. in = a CPU constrained system it becomes an "entangled metric" between= i/o and CPU though still presents in network i/o units which can be mislea= ding to network device vendors.

Also, many might want to consider mo= nitoring "network power" which is average throughput / latency or= delay, i.e. "something good" / "something bad"

= Bob

On Wed, Jul 17, 2019 at 3:26 PM Toke H=C3=B8iland-J=C3=B8rgensen &= lt;toke@redhat.com> wrote:
Bob McMahon <bob.mcmahon@broadco= m.com> writes:

> Just an FYI in case anybody has interest in traffic tooling.

I do! Specifically, I am planning to teach Flent to automatically switch between iperf and netperf as the underlying test tool[0]. I believe that there are a few netperf features missing from iperf that Flent currently uses, so I'll get back to you with actual feature requests for those once I've had a chance to take a look at this in more detail :)

-Toke

[0] The main driver for this is netperf's weird license which makes it<= br> impossible to package for FOSS-only distributions; leading to things
like this: https://bugzilla.redhat.com/show_bug= .cgi?id=3D1729939
--000000000000c7ff66058dfa72d7--