All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roy" <roy@xxx.lt>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IMQ Stability
Date: Sat, 24 Jan 2004 23:24:23 +0000	[thread overview]
Message-ID: <005a01c3e2d1$337ba7d0$030aa8c0@t> (raw)
In-Reply-To: <marc-lartc-105066408632475@msgid-missing>

Probably I am going to continue imq development, so I know about it
something.

IMQ is very unpredictable you can use it all week or it may crash at once.
and what is the most strange - crashes osccur everywhere in the kernel
except in the driver itself
this can be kernel bug as well.
under high loag it crashes quite soom while in low load it can hold forewer
this probably depends on cpu speed and looks that it tends to crash if you
try to shape localy generated trafic
if you use it for ingress only it wont have much problems.

I have no hope to make it work, I rewrote the code completely few times and
no use
probably this way just cant work.

I am going to use completely other way to do the same job.
imq is trying to use userspace queue which dont like when packets are droped
and seems there is no way to avoid droping
while doing trafic shaping, so I will use another way by completely removing
packets from iptables at some place and transmitting them directly where
needed.
thus replacing part of kernel code.
this way I will be able at least  to track the bug.

P.S. iptables have another similar module ( ROUTE target ) i tryed it and it
works in some cases ( i redirect trafic to lo interface) but not very good.


----- Original Message ----- 
From: "Michael S. Kazmier" <mkazmier@sofast.net>
To: <lartc@mailman.ds9a.nl>
Sent: Friday, January 23, 2004 7:29 PM
Subject: [LARTC] IMQ Stability


> Hello all,
>
> I have been doing a lot of archive searching over the last week reading
> posts on IMQ and it's apparent stability / instability.  I have seen a
> number of posts about it not being maintained as well.  Can anyone talk to
> me about IMQ's stability in a heavy throughput environment (20 Mbps) and
> what was causing IMQ to fail if you know.
>
> Thanks,
>
> Mike
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-01-24 23:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-18 11:28 [LARTC] IMQ Stability hare ram
2004-01-23 17:29 ` Michael S. Kazmier
2004-01-24 23:24 ` Roy [this message]
2004-01-24 23:38 ` mkazmier
2004-01-25  2:04 ` Alexander Clouter
2004-01-25  3:49 ` Roy
2004-01-25  8:56 ` Aron Brand
2004-01-26 10:36 ` Remus
2004-01-26 15:53 ` Michael S. Kazmier
2004-01-26 18:49 ` rubens
2004-01-27  0:39 ` Alexander Clouter
2004-01-28  8:25 ` Alexander Trotsai
2004-05-26 23:56 ` [LARTC] IMQ stability Damion de Soto
2004-05-28 22:21 ` Andre Correa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='005a01c3e2d1$337ba7d0$030aa8c0@t' \
    --to=roy@xxx.lt \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.