Hello lartc
I wrote a scheduling qdisc that works on a per-flow basis. It dequeue
packets according to a flow interval. But as it turns out there is a problem
with it.
The qdisc loads just fine and is working correctly. The problem is that if
the qdisc is removed and loaded again, it stops
Naturally I forgot to attach the code, as I was rushing to get to lunch.
R.harper
p.s why do my messages end up as a reply to someone else's message in the
archive?
_
Log på MSN Messenger direkte fra nettet
Hello
I am writing a qdisc scheduler (called fb in the diagram) that does certain
packet delaying and other stuff. (for egress traffic)
root (htb/tbf)
|
---
cl1 cl2|
tbf
||
Hell
I'm new to Qdisc programming and I was wondering, what is the difference
between using an internal Qdisc (like e.g. TBF does) vs. not using internal
Qdisc (like e.g. SFQ does)?
Can someone give me a quick rundown of pro and cons?
with regards
R.harper
/architectural difference between
creating a *internal Qdisc* for buffering (like TBF does) and then using
q-qdisc-enqueue(skb, q-qdisc) etc. commands for queueing ...
or just use the qdisc provided?
__skb_enqueue(skb, skq-q) etc commands for queueing
But thanks for your reply
Regards
R.Harper
R Harper
Hello
Can someone explane to me how the TCQ_F_THROTTLED flag and the watchdog
function used in tbf and htb works?
To be more specific, (reading tbf code)
if there are not enough tokens, a watchdog timer will be started and the
TCQ_F_THROTTLED flag set.
But what happens then the time is up?
