From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Jeremy Harris <jgh@wizmail.org>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] Netpower, iper2, BBR
Date: Sat, 4 Aug 2018 17:10:42 -0700 [thread overview]
Message-ID: <CAHb6LvqT8GwVDNXdScctfy8PV-+qNhVMq4FFR6y4=WpeHLK4Yg@mail.gmail.com> (raw)
In-Reply-To: <1b96c0a9-2362-9dde-d969-66101c2cfc78@wizmail.org>
[-- Attachment #1.1: Type: text/plain, Size: 994 bytes --]
It's a metric to determine if network congestion is being optimized.
Here's just one of many papers that use. This paper says that flow
controlled, per network power, can't be optimized with local information
only.
Bob
On Sat, Aug 4, 2018 at 3:47 PM, Jeremy Harris <jgh@wizmail.org> wrote:
> On 08/04/2018 06:55 PM, Bob McMahon wrote:
> > FYI, I've added a netpower metric to iperf 2.
> >
> > Below are two runs over wired GigE comparing Google's BBR
> > <https://ai.google/research/pubs/pub45646> with cubic. Note, for the
> > network power the delay units are microseconds while the throughput are
> > seconds.
>
> Why is it useful?
>
> It appears to be calculated as bandwidth divided by latency, so the
> units are bits / time^2. The word "power" in the naming feels
> misleading.
> --
> Cheers,
> Jeremy
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
[-- Attachment #1.2: Type: text/html, Size: 1780 bytes --]
[-- Attachment #2: NoDistFlowControl.pdf --]
[-- Type: application/pdf, Size: 649623 bytes --]
next prev parent reply other threads:[~2018-08-05 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 17:55 Bob McMahon
2018-08-04 22:47 ` Jeremy Harris
2018-08-05 0:10 ` Bob McMahon [this message]
2018-08-05 0:14 ` Bob McMahon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHb6LvqT8GwVDNXdScctfy8PV-+qNhVMq4FFR6y4=WpeHLK4Yg@mail.gmail.com' \
--to=bob.mcmahon@broadcom.com \
--cc=jgh@wizmail.org \
--cc=make-wifi-fast@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox