Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] benefits of other eyeballs on sqm
Date: Thu, 8 May 2014 10:41:08 +0200	[thread overview]
Message-ID: <095AF95D-8C32-4DF7-911C-EFCA10C0FDC0@gmx.de> (raw)
In-Reply-To: <CAA93jw6vNbJjSEj7ux=U_RQ_Z3DFywiBkLMDxEbj=FG1P6pHxQ@mail.gmail.com>

Hi Dave,


On May 7, 2014, at 21:28 , Dave Taht <dave.taht@gmail.com> wrote:

> http://community.ubnt.com/t5/EdgeMAX-Beta/Testing-fq-codel-in-v1-5-0beta1/m-p/828626/highlight/false#M3978
> 
> according to that script...
> 
> It turns out that ifb names can be symbolic rather than an integer,
> and thus a whole lot of ifb pool management stuff can get ripped out
> of the sqm system. probably.

	Well, the whole fib handling stuff I added tries to solve two problems; a) reuse the same fib we just used before for a specific interface, but do not steal fibs the user might have assigned by hand, and b) handle the intuition that no fib is available somewhat gracefully (note this still lacks an error message, and a bit of magic inside the *.qos scripts). Non-numeric IFB names potentially will make this more complicated, so I would rather stick to those… But you package and hence your decision.

Best Regards
	Sebastian

> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel


      reply	other threads:[~2014-05-08  8:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 19:28 Dave Taht
2014-05-08  8:41 ` Sebastian Moeller [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/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=095AF95D-8C32-4DF7-911C-EFCA10C0FDC0@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@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