From: Hagen Paul Pfeifer <hagen@jauu.net>
To: netdev@vger.kernel.org, "Motejlek, Petr" <pmotejle@akamai.com>
Cc: netem@osdl.org
Subject: Re: What queues/buffers does tc-netem use?
Date: Thu, 16 Jul 2015 15:04:19 +0200 (CEST) [thread overview]
Message-ID: <1880864426.2770.1437051859540.JavaMail.open-xchange@ox1app> (raw)
In-Reply-To: <1437050912759.32788@akamai.com>
> On July 16, 2015 at 2:48 PM "Motejlek, Petr" <pmotejle@akamai.com>
> wrote:
>
> Could you please give me some example of such a tc command that
> would tell me the statistics? I am not sure what you mean.
tc -s qdisc show dev eth0
> Is there a way I can manipulate the internal rbtree queue size, please?
Sure, the option is called limit.
> Thank you
You are welcome!
Hagen
prev parent reply other threads:[~2015-07-16 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 11:28 What queues/buffers does tc-netem use? Motejlek, Petr
2015-07-16 12:42 ` Hagen Paul Pfeifer
2015-07-16 12:48 ` Motejlek, Petr
2015-07-16 13:04 ` Hagen Paul Pfeifer [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1880864426.2770.1437051859540.JavaMail.open-xchange@ox1app \
--to=hagen@jauu.net \
--cc=netdev@vger.kernel.org \
--cc=netem@osdl.org \
--cc=pmotejle@akamai.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;
as well as URLs for NNTP newsgroup(s).