From: Dave Taht <dave.taht@gmail.com>
To: Justin McCann <jneilm@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Testing Queue models
Date: Wed, 1 Feb 2012 21:46:14 +0100 [thread overview]
Message-ID: <CAA93jw6pc0eBfc6WpUW472=V46o_y6_EyoAx16hCgoZKxevmow@mail.gmail.com> (raw)
In-Reply-To: <CAFkTFa__v9JmdWHzQPSupuExB4v6R-R27fRpz0XXPBrZG__9Sg@mail.gmail.com>
On Wed, Feb 1, 2012 at 9:08 PM, Justin McCann <jneilm@gmail.com> wrote:
> On Wed, Feb 1, 2012 at 12:12 PM, Dave Taht <dave.taht@gmail.com> wrote:
> It sounds to me like you want to assign each device its own netfilter
> MARK, and mark each packet (by MAC?) on ingress, and then use the mark
> plus any other port/protocol selection you want to put it into the
> appropriate queue.
the mark would be a unique id per mac, pulled from a small pool in a LRU
fashion. 256 - heck, 64, values for it - would be suitable for most homes
and small businesses.
As for the "plus" part - no, want to FQ across device id, and then FQ/AQM
within that, against all the streams coming from the device.
This would give 1/d fairness and (in particular) cope with bittorrent
pretty nicely.
I have a QFQ prototype which worked pretty well, in the debloat repo,
except for the unfairness of the per/ip and per/ipv6 hashing problem.
>
>> I tend to view (in the home) as having 1/u network performance as the
>> ideal. There are exceptions to this, notably video vs. say,
>> bittorrent. A clever way of getting closer to 1/u might be to sense
>> for more recent DNS queries and move that to a more interactive class.
>
> You might try assigning each device to a user, and then marking as
> above, assuming only one user at a time on a device.
requires manual assignment.
I've noted elsewhere that a users'
'attention' and normal usage pattern may be of interest in doing
it more automatically.
> I guess that doing this would address (in the local/home network) what
> Bob Briscoe was getting at in our earlier thread:
>
> "Since 2004, we now understand that fairness has to involve accounting
> over time. That requires per-user state, which is not something you
> can do, or that you need to do, within every queue. We should leave
> fairness to separate code, probably on machines specialising in this
> at the edge of a provider's network domain - where it knows about
> users/customers - separate from the AQM code of each specific queue."
Well, here we go... as mentioned in the conclusion of that thread,
1/d seems the best possible without having per-brain interfaces,
and 1/u seems to require some theoretical work, and in either case,
seems better than 1/f.
I don't have a whole lot of hope for classification. In fact, I'm kind of
upset that the move away from flash means we are seeing more
video streams on port 80, rather than on the macromedia port...
>
> Justin
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
FR Tel: 0638645374
http://www.bufferbloat.net
next prev parent reply other threads:[~2012-02-01 20:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 17:12 Dave Taht
[not found] ` <A8F77CC3-7B92-4979-A631-2921E66F1E95@gmx.de>
[not found] ` <CAA93jw50eQHiQHGh0V1z6vT1vxfo3ShJL8TAOprdCOiYHZAq3Q@mail.gmail.com>
2012-02-01 19:17 ` Sebastian Moeller
2012-02-01 19:49 ` Dave Taht
2012-02-01 20:08 ` Justin McCann
2012-02-01 20:38 ` Dave Taht
2012-02-01 20:46 ` Dave Taht [this message]
2012-02-15 2:08 ` Bruce Atherton
2012-02-17 14:22 ` Dave Taht
2012-02-17 21:55 ` Bruce Atherton
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6pc0eBfc6WpUW472=V46o_y6_EyoAx16hCgoZKxevmow@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=jneilm@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