From: Dev <dev@logicalwebhost.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] reatime buffer monitoring?
Date: Thu, 3 Jan 2019 18:06:43 -0800 [thread overview]
Message-ID: <55BCE9BD-B0CB-4A85-B476-5C8858E843E6@logicalwebhost.com> (raw)
In-Reply-To: <CAA93jw5Uj8vkE0eLgABbt8qxNVigf_FV40eLGsHH_rLGQYLejQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]
Okay, in case it’s of use to anyone else, here’s a quick howto for this tool:
apt-get install libncurses5-dev build-essential
git clone https://github.com/ffainelli/bqlmon.git <https://github.com/ffainelli/bqlmon.git>
cd bqlmon
make
./bqlmon -i eth0
HTH.
- Dev
> On Jan 3, 2019, at 2:31 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
> https://github.com/ffainelli/bqlmon is the official repo.
>
> On Thu, Jan 3, 2019 at 1:51 PM Pete Heist <pete@heistp.net> wrote:
>>
>> Since it looks like you have bql, this should work for the hardware queues: https://github.com/dtaht/bqlmon
>>
>> It might be nice to have a realtime monitor for the qdisc stats, but these can also change very quickly so looking at drops and marks, or other stats, can be useful as well.
>>
>> On Jan 3, 2019, at 10:23 PM, Dev <dev@logicalwebhost.com> wrote:
>>
>> Is there a command to watch what the buffer is doing real time once I run traffic across it, or some way to know what it’s doing?
>>
>> I’m experimenting with something like:
>>
>> watch -n 1 tc -g -s class show dev eth0
>>
>> But I gotta guess there’s a better way to do this?
>>
>> - Dev
>>
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>>
>>
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>
>
>
> --
>
> Dave Täht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-205-9740
[-- Attachment #2: Type: text/html, Size: 3148 bytes --]
prev parent reply other threads:[~2019-01-04 2:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 17:32 [Bloat] fq_codel on bridge multiple subnets? Dev
2019-01-03 18:12 ` Toke Høiland-Jørgensen
2019-01-03 18:54 ` Pete Heist
2019-01-04 5:22 ` Dev
2019-01-04 9:19 ` Pete Heist
2019-01-04 18:20 ` Dev
2019-01-04 18:57 ` Dave Taht
2019-01-04 20:33 ` [Bloat] fq_codel on bridge throughput test/config Dev
2019-01-04 20:40 ` Toke Høiland-Jørgensen
2019-01-16 0:54 ` Dev
2019-01-05 0:17 ` Stephen Hemminger
2019-01-03 21:23 ` [Bloat] reatime buffer monitoring? Dev
2019-01-03 21:51 ` Pete Heist
2019-01-03 22:31 ` Dave Taht
2019-01-04 2:06 ` Dev [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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55BCE9BD-B0CB-4A85-B476-5C8858E843E6@logicalwebhost.com \
--to=dev@logicalwebhost.com \
--cc=bloat@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