From: Jonathan Morton <chromatix99@gmail.com>
To: David Lang <david@lang.hm>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Cake List" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] arp flow dissector
Date: Mon, 3 Sep 2018 16:00:10 +0300 [thread overview]
Message-ID: <F785D88B-BB69-4908-B92C-E679021F1024@gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1809030529130.4352@qynat-yncgbc>
> On 3 Sep, 2018, at 3:29 pm, David Lang <david@lang.hm> wrote:
>
> how much ARP traffic would there have to be before the benefits of this outweigh the overhead of tracking it?
If there's very little ARP traffic (as normal), then the overhead of recognising it is basically nil.
The benefits become apparent as soon as the volume of ARP traffic, in aggregate, becomes great enough for its queue to be marked "saturating" instead of "sparse". This could reasonably occur if the other traffic consists of a lot of distinct flows.
- Jonathan Morton
prev parent reply other threads:[~2018-09-03 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 19:37 Dave Taht
2018-09-03 1:36 ` Jonathan Morton
2018-09-03 11:14 ` Toke Høiland-Jørgensen
2018-09-03 12:26 ` Jonathan Morton
[not found] ` <nycvar.QRO.7.76.6.1809030529130.4352@qynat-yncgbc>
2018-09-03 13:00 ` Jonathan Morton [this message]
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F785D88B-BB69-4908-B92C-E679021F1024@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=toke@toke.dk \
/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