Historic archive of defunct list cerowrt-commits@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: noreply@github.com
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/deBloat] 23733e: Mildly better version with a test that seems to sh...
Date: Thu, 29 Dec 2011 04:20:46 -0800	[thread overview]
Message-ID: <20111229122046.E3771425B2@smtp1.rs.github.com> (raw)

  Branch: refs/heads/master
  Home:   https://github.com/dtaht/deBloat

  Commit: 23733e3d4965e12465f1bb9c78b9413ef184be87
      https://github.com/dtaht/deBloat/commit/23733e3d4965e12465f1bb9c78b9413ef184be87
  Author: Dave Taht <d@taht.net>
  Date:   2011-12-29 (Thu, 29 Dec 2011)

  Changed paths:
    M src/classify.lua
  M src/diffserv.lua
  A src/testrules.sh

  Log Message:
  -----------
  Mildly better version with a test that seems to show mq broken

It's really odd. NOTHING ever ends up in any queue other than
1:3. It's not clear where classification should be happening,
or if (maybe) the wireless driver is blithly overridding
my painstakingly setup iptables scheme.

There's still plenty of other bugs, but, now I'm puzzled
about some kernel level stuff.



                 reply	other threads:[~2011-12-29 12:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

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

  git send-email \
    --in-reply-to=20111229122046.E3771425B2@smtp1.rs.github.com \
    --to=noreply@github.com \
    --cc=cerowrt-commits@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