From: Sami Farin <safari@iki.fi>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB not that exact
Date: Fri, 07 Dec 2001 16:57:39 +0000 [thread overview]
Message-ID: <marc-lartc-100779926629246@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100766696815760@msgid-missing>
On Thu, Dec 06, 2001 at 08:48:11PM +0100, bert hubert wrote:
> On Thu, Dec 06, 2001 at 08:28:07PM +0100, Stefan Rompf wrote:
...
> > tbf seems not to be able to do exact rate limiting, too. Anything wrong
> > in my configuration, or am I just taking false statistics?
>
> Both I think. There are some indications that raising HZ may not work, as it
> may not raise the resolution of the timers in the Linux Kernel - I am
> investigating this! So try keeping HZ stable, and raising the size of your
> bucket.
would it make any difference if you do...
--- linux/include/net/pkt_sched.h.bak Sun Nov 19 20:14:10 2000
+++ linux/include/net/pkt_sched.h Sun Nov 19 20:20:34 2000
@@ -5,7 +5,7 @@
#define PSCHED_JIFFIES 2
#define PSCHED_CPU 3
-#define PSCHED_CLOCK_SOURCE PSCHED_JIFFIES
+#define PSCHED_CLOCK_SOURCE PSCHED_CPU
#include <linux/config.h>
#include <linux/pkt_sched.h>
I didn't see PSCHED_CLOCK_SOURCE in the 2.4routing docs...
Can you tell more about PSCHED_CLOCK_SOURCE ?
--
Safari - safari@iki.fi - PGP key 0x427E7914 - http://www.iki.fi/safari/
The UNIX Guru's View of Sex: "unzip ; strip ; touch ; finger ; \
mount ; fsck ; more ; yes ; umount ; sleep"
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-12-07 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 19:28 [LARTC] HTB not that exact Stefan Rompf
2001-12-06 19:48 ` bert hubert
2001-12-06 20:33 ` Daniel Ryczek
2001-12-06 21:35 ` Stefan Rompf
2001-12-07 11:46 ` david
2001-12-07 16:57 ` Sami Farin [this message]
2001-12-08 8:51 ` Martin Devera
2001-12-08 11:52 ` bert hubert
2001-12-08 11:53 ` bert hubert
2001-12-08 15:18 ` devik
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=marc-lartc-100779926629246@msgid-missing \
--to=safari@iki.fi \
--cc=lartc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox