From: Patrick McHardy <kaber@trash.net>
To: leon zadorin <leonleon77@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: "no hz"/"dynamic tick" option and TC/TBF (token bucket filter) behaviour...
Date: Thu, 05 Apr 2007 16:48:41 +0200 [thread overview]
Message-ID: <46150C49.4050800@trash.net> (raw)
In-Reply-To: <26d2cb010704050736y775b6b09g67fd40344cd2208d@mail.gmail.com>
leon zadorin wrote:
> 2) for kernels which do have the aforementioned option enabled: how
> does this affect the "tc" (traffic control) utility and the Token
> Bucket Filter (tbf) queueing discipline (traffic-smoothing)
> behhaviour?
>
> For example, the TBF doco suggests that due to the whole fixed Hz
> thing in the kernel (e.g. 100Hz) the maximum rate of the TBF would
> actually be limited to say 1mbit on Intel arch (with the default
> mtu... but if mtu is incleased, so is the burstiness of the traffic
> which is what TBF is trying to prevent in my deployment scenarios).
> ...
>
> So what about the kernels which use this "dyna tick" option - in such
> a kernel, will there be an interrupt generated (e.g. at microsec.
> precision on most platforms) for every packet's send time (e.g. say at
> TBF's rate is at 25Mbps and one sends out 1KB data packets... will
> there be an interrput generated every... 300 microseconds?)...
No, it doesn't affect the timer resolution. net-2.6.22 includes
patches that switch all qdiscs to hrtimers, which allows to use
much smaller burst rates.
prev parent reply other threads:[~2007-04-05 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 14:36 "no hz"/"dynamic tick" option and TC/TBF (token bucket filter) behaviour leon zadorin
2007-04-05 14:48 ` Patrick McHardy [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=46150C49.4050800@trash.net \
--to=kaber@trash.net \
--cc=leonleon77@gmail.com \
--cc=linux-kernel@vger.kernel.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 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.