From: i@introo.me (Shiyao Ma)
To: kernelnewbies@lists.kernelnewbies.org
Subject: how to periodically monitor the qdisc size ?
Date: Thu, 29 Dec 2016 23:04:19 +0800 [thread overview]
Message-ID: <CAJQX3DwyWN89aBX=EKH0TKb6zev_QN6MKiPHPD-kH7cPiin8Mw@mail.gmail.com> (raw)
In-Reply-To: <CAEzD07KtgFxkuF5AZs9jJKSzn8zFq7TiNf+iNtdAaxa27jeGtg@mail.gmail.com>
Hi Anton,
Thanks for your reply. Now problem solved.
A minor question is, is there any official documentation on the entry
meaning, such as `backlog' ?
I checked the related manpage, but found none.
Or indeed, tc is not thoroughly documented, and one has to check unofficial
web blogs?
(BTW, I grepped the iproute2 source, and then found this
file: iproute2-4.9.0/include/linux/gen_stats.h which helps to explains
what `backlog' is.).
On Thu, Dec 29, 2016 at 9:49 PM, Anton Danilov <littlesmilingcloud@gmail.com
> wrote:
> Hi.
> You can use 'tc -s qdisc list dev <iface>' and check the 'backlog' line -
> it's current queue status.
>
>
> 2016-12-28 10:16 GMT+03:00 Shiyao Ma <i@introo.me>:
>
>> Hi,
>>
>> I am using the RED qdsic.
>>
>> I want to see how many skbuffs are in the red qdisc, and the total bytes
>> of the skbuffs, like in every 2 seconds.
>>
>>
>> Regards
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
>>
>
>
> --
> Anton.
>
--
????????????????https://introo.me <http://introo.me>?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161229/027ede3a/attachment.html
next prev parent reply other threads:[~2016-12-29 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-28 7:16 how to periodically monitor the qdisc size ? Shiyao Ma
2016-12-29 13:49 ` Anton Danilov
2016-12-29 15:04 ` Shiyao Ma [this message]
[not found] ` <175748.1483036132@turing-police.cc.vt.edu>
2016-12-29 23:27 ` Shiyao Ma
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='CAJQX3DwyWN89aBX=EKH0TKb6zev_QN6MKiPHPD-kH7cPiin8Mw@mail.gmail.com' \
--to=i@introo.me \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).