From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/deBloat] : Document how I use the pdsh utility and libgenders...
Date: Sun, 08 Jan 2012 12:34:21 -0800 [thread overview]
Message-ID: <4f09fdcd14a26_67513fe0766cc2f82007be@sh1.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1844 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/deBloat
Commit: 71d475772130ea2cc717226727162df2b5dfb26a
https://github.com/dtaht/deBloat/commit/71d475772130ea2cc717226727162df2b5dfb26a
Author: Dave Taht <d@taht.net>
Date: 2012-01-08 (Sun, 08 Jan 2012)
Changed paths:
A test/lab2.genders
A test/lab2.hosts
Log Message:
-----------
Document how I use the pdsh utility and libgenders db
When coping with a cluster, you gain enormous power
via tools to manage it.
Commit: 4d023e193155b1112b101b058d514da6f8d0f791
https://github.com/dtaht/deBloat/commit/4d023e193155b1112b101b058d514da6f8d0f791
Author: Dave Taht <d@taht.net>
Date: 2012-01-08 (Sun, 08 Jan 2012)
Changed paths:
M src/staqfq.lua
Log Message:
-----------
Added working openwrt and basic sfq support to staqfq script
I had intended to break this apart (2nd system syndrome)...
instead I'm glopping on features until I truly do need to
refactor....
Anyway, this points out that sch_mq doesn't DO THE RIGHT THING
for VOIP, nor multicast... everything ends up in the BE queue
for some reason, which is a bad idea...
Commit: fefdca793fabc72716cc32cdfa32e91f4e078412
https://github.com/dtaht/deBloat/commit/fefdca793fabc72716cc32cdfa32e91f4e078412
Author: Dave Taht <d@taht.net>
Date: 2012-01-08 (Sun, 08 Jan 2012)
Changed paths:
A test/bin/labup
Log Message:
-----------
simple script to see if the lab is up
Commit: 92890a7d253372cc3448c605f4ea627fc7a84c87
https://github.com/dtaht/deBloat/commit/92890a7d253372cc3448c605f4ea627fc7a84c87
Author: Dave Taht <d@taht.net>
Date: 2012-01-08 (Sun, 08 Jan 2012)
Changed paths:
M src/staqfq.lua
Log Message:
-----------
some notes on sfq
Compare: https://github.com/dtaht/deBloat/compare/7f093ed...92890a7
reply other threads:[~2012-01-08 20:34 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=4f09fdcd14a26_67513fe0766cc2f82007be@sh1.rs.github.com.mail \
--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