From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] esfq experience anyone?
Date: Sat, 26 Apr 2003 14:53:50 +0000 [thread overview]
Message-ID: <marc-lartc-105136887506287@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105134946328373@msgid-missing>
On Saturday 26 April 2003 16:47, Nickola Kolev wrote:
> On Sat, 26 Apr 2003 15:07:52 +0200
>
> Matthias Weingart <lartc@pentax.boerde.de> wrote:
> : On Sat, Apr 26, 2003 at 12:29:12PM +0300, Nickola Kolev wrote:
> : > Did anyone tried it, and more important, did it worked the way it is
> : > supposed to? As of my experience, I saw several connections matched
> : > right against the filters and put into the correct class, but the
> : > bandwidth management wasn't even remotely fair.
> :
> : Did you use a kernel with
> : #define PSCHED_CLOCK_SOURCE PSCHED_CPU in
> : linux/include/net/sched/pkt_sched.h or just the standard kernel?
> :
> : Matthias
>
> Nope,
>
> The place for pkt_sched.h here is linux/include/net/pkt_sched.h.
> And there #define PSCHED_CLOCK_SOURCE PSCHED_JIFFIES
>
> Can you tell me what's the difference? I mean, I see that in your
> case clock source for packet scheduling is #defined as PSCHED_CPU,
> and in mine as PSCHED_JIFFIES, but what's the impact on esfq?
About the difference :
http://www.docum.org/stef.coene/qos/faq/cache/40.html
The impact is increased precision.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-04-26 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-26 9:29 [LARTC] esfq experience anyone? Nickola Kolev
2003-04-26 13:07 ` Matthias Weingart
2003-04-26 14:47 ` Nickola Kolev
2003-04-26 14:53 ` Stef Coene [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=marc-lartc-105136887506287@msgid-missing \
--to=stef.coene@docum.org \
--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 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.