From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages-3.10] 809046: Add flent-tc_iterate to be able to quickly inspect...
Date: Wed, 02 Dec 2015 10:54:46 -0800 [thread overview]
Message-ID: <565f3e7613d91_7e793fa2a4d612b8180449@hookshot-fe1-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages-3.10
Commit: 809046bfae287df61bd3d06edd84f3178fd31587
https://github.com/dtaht/ceropackages-3.10/commit/809046bfae287df61bd3d06edd84f3178fd31587
Author: CeroWrt Admin <dave.taht@bufferbloat.net>
Date: 2015-12-02 (Wed, 02 Dec 2015)
Changed paths:
A net/flent/Makefile
Log Message:
-----------
Add flent-tc_iterate to be able to quickly inspect queue depth
Looking at queue depth at high rates (say 20ms intervals) has a
tendency to heisenbug the data. Hopefully this version of the
tc_iterate code, reduced to pure C will prove fast enough
to run on a regular basis on openwrt derived devices.
reply other threads:[~2015-12-02 18:54 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=565f3e7613d91_7e793fa2a4d612b8180449@hookshot-fe1-cp1-prd.iad.github.net.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