Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Valdis.Kletnieks@vt.edu
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Fwd: next round of SQM changes
Date: Thu, 9 Oct 2014 23:14:53 +0200	[thread overview]
Message-ID: <1323910A-D2C8-4D33-ADE9-9A65AD3A6BB8@gmx.de> (raw)
In-Reply-To: <17521.1412888088@turing-police.cc.vt.edu>

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

Hi Valdis,


On Oct 9, 2014, at 22:54 , Valdis.Kletnieks@vt.edu wrote:

> On Thu, 09 Oct 2014 22:37:30 +0200, Sebastian Moeller said:
>> I am again in need of testers for SQM.
> 
> Sure, what's needed to get the testable bits onto a 3.10.50-1 box?
> 

The attached archaic contains all SQM related files that I changed compared to stock cerowrt 3.10.50-1. So all that should be required is to replace the files in /usr with the files from the archive. The change in /usr/lib/lua just exposes more interfaces to the GUI (and I am not yet sure whether that is a sane idea or not). The changes in /usr/lib/sqm implement the changes: more robots tear down of active SQM instances, and a switch from indexes IFB devices ala ifb0 to names fib devices ala ifb4ge00 to sanitize IFB handling somewhat. Hopefully these last changes make cerowrt way more robust against accidental left over shaping instances.
	Thanks for volunteering to test…

Best Regards
	Sebastian



[-- Attachment #2: sqm_test_141009.tar.gz --]
[-- Type: application/x-gzip, Size: 9060 bytes --]

      reply	other threads:[~2014-10-09 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09 20:18 [Cerowrt-devel] " Sebastian Moeller
2014-10-09 20:37 ` [Cerowrt-devel] Fwd: " Sebastian Moeller
2014-10-09 20:54   ` Valdis.Kletnieks
2014-10-09 21:14     ` 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=1323910A-D2C8-4D33-ADE9-9A65AD3A6BB8@gmx.de \
    --to=moeller0@gmx.de \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=cerowrt-devel@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