CoDel AQM discussions
 help / color / mirror / Atom feed
From: Richard Edmands <thesirdmz@gmail.com>
Cc: codel <codel@lists.bufferbloat.net>
Subject: Re: [Codel] Floating an Idea. ip_fq_codel
Date: Fri, 20 Jun 2014 19:35:00 +1000	[thread overview]
Message-ID: <CAGNxc=zoVm8gmGQPxpjzqYGKhHcXJeYUwnTkhD1dVdaxY-YBNA@mail.gmail.com> (raw)
In-Reply-To: <1402106170.6343.3.camel@ganymede.home>

[-- Attachment #1: Type: text/plain, Size: 1750 bytes --]

With the tc filter flow hash keys i've been having problems verifying if
they've been installed. I've searched the man pages and haven't found the
solution. It "should" be tc filter show dev *insert dev*
but that doesn't list them :(
any ideas what i've missed.



tc filter add dev eth0 protocol ip parent 1: handle 1 \
        flow hash keys dst divisor 8192


On Sat, Jun 7, 2014 at 11:56 AM, Dan Siemon <dan@coverfire.com> wrote:

> On Tue, 2014-05-20 at 19:15 +1000, Richard Edmands wrote:
> > In my environment we've got a fair chunk of torrent usage happening (+
> > gaming) and with fq_codel giving the advantage to whichever individual
> > could open up as many connections as possible the entire situation
> > imploded very quickly.
> >
> > So to balance this out I used htb to implement the IP part of this
> > (actually not really, i made groups of ip's which belonged to
> > individuals) and stuck fq_codel on top of the divided setup.
> >
> > With this system what now happens is each IP now gets equal
> > utilization of the link (actually, i'm a lazy hack. I only implemented
> > the uplink section) which prevents the advantage of opening up as many
> > connections as possible.
> > Now when an individual decides to go nuts, they're limited to what is
> > available to them without harming everyone else, without compromising
> > maximum possible speed.
> >
> >
> > I have had this running in my environment for the past month and WOW.
>
> I did something similar as well. You can find the script and results
> below. Let me know if you find any bugs.
>
>
> http://git.coverfire.com/?p=linux-qos-scripts.git;a=blob;f=src-3tos.sh;hb=HEAD
>
>
> http://www.coverfire.com/archives/2013/01/01/improving-my-home-internet-performance/
>
>

[-- Attachment #2: Type: text/html, Size: 3496 bytes --]

  reply	other threads:[~2014-06-20  9:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20  9:15 Richard Edmands
2014-05-20 10:16 ` Andrew McGregor
2014-05-20 14:34   ` Dave Taht
2014-05-20 15:31   ` Eric Dumazet
2014-05-20 15:38     ` Eric Dumazet
2014-05-21  0:15     ` Andrew McGregor
2014-06-07  1:56 ` Dan Siemon
2014-06-20  9:35   ` Richard Edmands [this message]
2014-06-20 17:04     ` Dave Taht

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/codel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGNxc=zoVm8gmGQPxpjzqYGKhHcXJeYUwnTkhD1dVdaxY-YBNA@mail.gmail.com' \
    --to=thesirdmz@gmail.com \
    --cc=codel@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