> On Wed, 29 Nov 2023 00:12:02 +0300
> 4 <babut@yandex.ru> wrote:
>> i haven't used queues for a long time, but now there is a need.
>> previously, queues had not only a hierarchy, but also a priority. now
>> there is no priority, only the hierarchy exists.
> It took me quite some time to wrap my head around this, having been
> accustomed to HFSC up until 5.5. One can probably find a lot of my
> emails in misc@ archives from that time.
> Nowadays I am matching traffic to prio and queue by protocol and/or
> destination port only. Anything not explicitly matched goes to lowest prio
> queue and logged even when passed, so I can inspect if there are any
> types of traffic which should be put into appropriate prio / queue. All
> the ACKs except those in lowest prio queue get highest (7) priority,
> stuff in lowest prio have lowest prio for ACKs as well.
> # QUEUE MATCHES
> match proto icmp set prio ( 6 7 ) queue ( 6-fly 7-ack ) tag queued
<skiped>
match proto icmp set prio(6 7) queue(6-fly 7-ack)
how is this supposed to work at all? i.e. packets are placed both in prio's queues 6/7(in theory priorities and queues are the same thing), and in hsfc's queues 6-fly/7-ack at once? i am surprised that this rule does not cause a syntax error. it looks interesting(i didn't know it was possible. is this definitely not a bug? :D), but still i don't understand the intent %\ i need to think about it and experiment. thank you, it was very valuable information!
No comments:
Post a Comment