Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Outback Dingo <outbackdingo@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] edgerouter LTE beta w/fq_codel upcoming
Date: Wed, 23 Apr 2014 13:05:47 -0400	[thread overview]
Message-ID: <CAKYr3zznwvBVAtOc-p_z_eepLYgs75y_za7VA65vsrV8QWt8Cw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4u022VycOTodDDOO+Nk7aR-0Fp8qjVKt-YT2+Oy1rumA@mail.gmail.com>

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

You obviously mean edgerouter LITE right? there is no LTE wireless
edgerouter, though that would be nice as a backup/failover


On Wed, Apr 23, 2014 at 11:53 AM, Dave Taht <dave.taht@gmail.com> wrote:

> As I pointed out here,  there is more work to be done  on that  front
>
>
> http://community.ubnt.com/t5/EdgeMAX/S-FQ-CoDel-Support-Possible/m-p/799394#M28651
>
> Mostly  my hope  is to get a SQM-like shaper/aqm/scheduler rewritten
> in  the vyatta command  language that works at  rates  up  to 200Mbit.
>
> All the published examples  have problems:
>
> http://www.five-ten-sg.com/mapper/bufferbloat  for  example,  uses SFQ
> and a very small queue length that is probably ineffective.
>
> There  have been various other  examples forwarded to  me that all
> need  some love,
> including  one  very elaborate one that uses ifb semi-correctly, and
> then goes nutso  with
> ack prioritization.  (can't find any of these now)
>
> ...
>
> And  it did look that adding BQL support was easily possible for  the
> underlying driver,  but I didn't  sink  any time  into  that  - the
> key "driver" (it's really an  interface   to a binary blob) is  in:
>
> drivers/net/ethernet/octeon
>
> and  it's  unclear  how much buffering is built into  the blob.
>
> --
> Dave Täht
>
> NSFW:
> https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

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

      reply	other threads:[~2014-04-23 17:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23 15:53 Dave Taht
2014-04-23 17:05 ` Outback Dingo [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=CAKYr3zznwvBVAtOc-p_z_eepLYgs75y_za7VA65vsrV8QWt8Cw@mail.gmail.com \
    --to=outbackdingo@gmail.com \
    --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