From: Stephen Hemminger <stephen@networkplumber.org>
To: Russell Strong <russell@strong.id.au>
Cc: netdev@vger.kernel.org
Subject: Re: amplifying qdisc
Date: Wed, 8 Jul 2020 23:26:34 -0700 [thread overview]
Message-ID: <20200708232634.0fa0ca19@hermes.lan> (raw)
In-Reply-To: <20200709161034.71bf8e09@strong.id.au>
On Thu, 9 Jul 2020 16:10:34 +1000
Russell Strong <russell@strong.id.au> wrote:
> Hi,
>
> I'm attempting to fill a link with background traffic that is sent
> whenever the link is idle. To do this I've creates a qdisc that will
> repeat the last packet in the queue for a defined number of times
> (possibly infinite in the future). I am able to control the contents of
> the fill traffic by sending the occasional packet through this qdisc.
>
> This is works as the root qdisc and below a TBF. When I try it as a
> leaf of HTB unexpected behaviour ensues. I suspect my approach is
> violating some rules for qdiscs? Any help/ideas/pointers would be
> appreciated.
Netem can already do things like this. Why not add to that
next prev parent reply other threads:[~2020-07-09 6:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 6:10 amplifying qdisc Russell Strong
2020-07-09 6:26 ` Stephen Hemminger [this message]
2020-07-12 1:40 ` Russell Strong
2020-07-13 16:52 ` Stephen Hemminger
2020-07-20 1:39 ` Russell Strong
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=20200708232634.0fa0ca19@hermes.lan \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=russell@strong.id.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.