From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] More overhead keywords
Date: Fri, 22 May 2015 17:30:16 -0700 [thread overview]
Message-ID: <CAA93jw5Xv00notN8Pg2jFhhwx2g6xHECwPprVE8ZfZtmivLSBA@mail.gmail.com> (raw)
In-Reply-To: <AE88AA8A-6B7A-4FCB-A482-66659015802D@gmail.com>
I had a thought. the flow_dissector stuff already has a ton of stuff
in it for breaking apart various frame types already, instead of
specifying (at least some of these) options, we could inspect the
traffic itself and set things more automagically?
next prev parent reply other threads:[~2015-05-23 0:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 14:02 [Cake] openwrt build with latest cake and other qdiscs Alan Jenkins
2015-05-10 17:29 ` Alan Jenkins
2015-05-10 20:37 ` Dave Taht
2015-05-10 20:38 ` Dave Taht
2015-05-11 6:54 ` Sebastian Moeller
2015-05-10 21:46 ` Sebastian Moeller
2015-05-10 22:19 ` Dave Taht
2015-05-11 6:50 ` Sebastian Moeller
2015-05-11 7:01 ` Jonathan Morton
2015-05-13 6:43 ` Jonathan Morton
2015-05-14 9:19 ` Sebastian Moeller
2015-05-14 10:24 ` Jonathan Morton
2015-05-14 10:33 ` Alan Jenkins
2015-05-14 10:42 ` Jonathan Morton
2015-05-14 10:58 ` Sebastian Moeller
2015-05-14 13:12 ` Jonathan Morton
2015-05-14 14:57 ` Sebastian Moeller
2015-05-14 15:32 ` Jonathan Morton
2015-05-14 18:15 ` Sebastian Moeller
2015-05-14 22:06 ` Jonathan Morton
2015-05-15 2:27 ` Dave Taht
2015-05-15 21:49 ` Jonathan Morton
2015-05-14 9:50 ` Alan Jenkins
2015-05-18 0:49 ` [Cake] More overhead keywords Jonathan Morton
2015-05-18 7:27 ` Sebastian Moeller
2015-05-18 8:13 ` Jonathan Morton
2015-05-18 8:41 ` Sebastian Moeller
2015-05-18 19:41 ` David Lang
2015-05-18 19:57 ` Dave Taht
2015-05-19 10:14 ` Kevin Darbyshire-Bryant
2015-05-23 0:30 ` Dave Taht [this message]
2015-05-23 2:27 ` Jonathan Morton
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=CAA93jw5Xv00notN8Pg2jFhhwx2g6xHECwPprVE8ZfZtmivLSBA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
/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