Skip to contentSkip to conversation

VQs in Gred!

DISCUSSION Zhenyu Wu 2 participants 2 messages Dec 30, 2004

lore
Share & tools
lore

Zhenyu Wu

author
#0 lore raw
Quoted 6 lines
Quoted 2 lines

HOW does the Gred schedule packets of differnet priorities?

The packets are all enqueued onto the same queue. Gred is not about prioritizing but only about dropping, hence once the packet is enqueued it doesn't make sense to differ anymore. The difference

Ok. Then, if the average packet(qave) does not exceed the threshhold, that is, the packet has not been dropped, it will be enqueued into the physical queue, right? So we can't see the different process of scheduling packets which are from different kinds of traffic, we just know which packet might be dropped, right?

Quoted 5 lines

to normal red is that one can use separate red calculation parameters per tcindex flow. tcindex is usually set via dsmark/ tcindex with contents of the dscp field. You might want to use a more aggressive set of parameters for your bulk flows and treat your interactive flows with more respect.

what does "the more aggressive set of parameters" mean? The parameters to Gred?

Thank you very much!
Best,

#1 lore raw
Quoted 4 lines

Ok. Then, if the average packet(qave) does not exceed the threshhold, that is, the packet has not been dropped, it will be enqueued into the physical queue, right? So we can't see the different process of scheduling packets which are from different kinds of traffic, we just know which packet might be dropped, right?

Right, all packets, regardless of type, colour, flavour, whatever are enqueued onto the same skb queue. You can always put a cbq/htb qdisc underneath and have gred be the leaf qdisc so you can do the prioritizing before gred. Be warned, heavy dropping in a gred leaf qdisc corrupts any rate estimations in prio qdiscs.

Quoted 1 line

what does "the more aggressive set of parameters" mean? The parameters to Gred?

Yes, struct gred_sched_data.