From: Andy Furniss <andy.furniss@dsl.pipex.com>
Cc: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: Re: IMQ Replacement
Date: Tue, 27 Jan 2004 08:24:19 +0000 [thread overview]
Message-ID: <40162033.4040701@dsl.pipex.com> (raw)
In-Reply-To: <4015AE11.1090607@dsl.pipex.com>
Andy Furniss wrote:
> Andy Furniss wrote:
>
>> There is also discussion on the LARTC list at the moment - someone
>> called roy has rewritten IMQ but still sees crashes. He thinks they
>> are related to locally generated traffic, so IMQ for ingress should be
>> OK.
>
>
> He just posted this, thought it may be of interest.
>
>
> 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 imq.
> you can find it on my server http://pupa.da.ru
> please tell how it works for you and how stable it is.
He has since posted that it crashes on locally generated traffic,
apparently the kernel resends what gets dropped and at 100mbs this uses
too many resources.
Andy.
next prev parent reply other threads:[~2004-01-27 8:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 15:56 linux-2.4.22, iptables-1.2.9, imq Josh Howlett
2003-11-13 12:45 ` Vigil
2004-01-17 15:15 ` IMQ Replacement Peter Frischknecht
2004-01-19 13:33 ` Andre Correa
2004-01-20 1:26 ` Rio Martin
2004-01-20 10:28 ` Remus
2004-01-20 22:04 ` Alex Satrapa
2004-01-20 11:05 ` Krystian
2004-01-21 14:52 ` Andre Correa
2004-01-26 12:16 ` Andre Correa
2004-01-26 14:42 ` Sven Schuster
2004-01-26 15:50 ` Andy Furniss
2004-01-27 0:17 ` Andy Furniss
2004-01-27 8:24 ` Andy Furniss [this message]
2004-01-27 8:13 ` Remus
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=40162033.4040701@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--cc=netfilter@lists.netfilter.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.