Dimitris Kotsonis wrote:
Using htb you could have each user hitting a separate class, each
with a RATE and a common CEIL so that they can all burst if the
line isnt contended... Then feed each of those that info BFIFO
with limit set just over 2x MTU sized packets (if the connection is
relatively slow). Alternatively if your O/S has it check out
fq_codel.
I could do that but for a class C lan I would have to create 256
seperate classes and 256 separate filters. Each for every ip. Whereas
in SFQ you only have to specify that the hashing algorithm should
work on the dst field & 0xFF and everything works automatically. For
more than 256 ips things will get really clattered. Also I wonder if
speed is an issue here with so many rules.
I don't think 256 is that much depending on h/w of course, You can hash
filters and using htb would let you do more eg. give priority to small
packets per user.
If you really want sfq, then to limit one user and go onto one sfq I
think you would need to look into ifb so you could double process some
packets.
--
To unsubscribe from this list: send the line "unsubscribe lartc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
