Roy wrote:
Seems I was to fast to declare success,
my version is not much more stable than the original one,everything depends
on dropped packets.
This is even not imq fault afterall, can be prowed in other way also:
atempts to police outgoing trafic it will be ok until you dont touch localy
[snip]
I noticed that with my trafic counter. internal trafic grew to enormous
levels 10X more than it can be. In reality there was almost no output at
all.
so DONT USE POLICERS ON EGRESS. on low trafic it is harmless but on
100mb/s it probably can kill computer (not tested).
Seems imq have
Finaly I made imq driver stable it did not crashed for all 5 hours under
high load, soo looks stable.
(old one was crashing after 1-5 min for me)
no need to patch anything just compile and insmod, should work with any
kernel probably must be than 2.4.20
This is completely diferent code than old
Finaly I made imq driver stable it did not crashed for all 5 hours under
high load, soo looks stable.
(old one was crashing after 1-5 min for me)
It seems to capture ingress and egress traffic of all interfaces; wouldn't
this count packets twice ?
If the machine is doing SNAT or DNAT, what
Seems I was to fast to declare success,
my version is not much more stable than the original one,everything depends
on dropped packets.
This is even not imq fault afterall, can be prowed in other way also:
atempts to police outgoing trafic it will be ok until you dont touch localy
generated
Hi.
Roy wrote:
Finaly I made imq driver stable [...]
This is completely diferent code than old imq.
May I then second the proposal to give the driver another name? How
about IMQ2, IMQng (next generation) or something like that?
Bye, Mike
___
LARTC
