From: "Roy" <roy@xxx.lt>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IMQ patch for iptables-1.2.9 and kernel 2.6.2 final !
Date: Fri, 20 Feb 2004 18:21:05 +0000 [thread overview]
Message-ID: <005f01c3f7de$4e463450$030aa8c0@t> (raw)
In-Reply-To: <Pine.LNX.4.58.0402191815410.21441@fly-net.ro>
> Hi, I'm sorry for not being able to be really polite this time, but:
>
> Roy, can you please STOP telling that egress crashs IMQ!?
You are to late, I anot teling thi anymore, and I even wont use
ingres and egress definitions anymore because they may cause
missundersatndings.
the better ones are input forward and output.
This my post is probably too old to reply.
seems I forgot to fix it on my page, I will do this now.
But I cant edit or erase it from mailing list afterall !
> We've discussed it lots of times before, here and at linuximq mailling
> list and the only known functionality that crashs IMQ (oriinal) is to
> touch local generated traffic...
That is correct.
> I've being using ingress+egress with IMQ in a server with a great
> amouunt of traffic, for a long period without any crashs.
>
> Please don't keep telling something known to be wrong or otherwise
> proove it so we can fix it...
As I told before I just used incorrect definitions,
I will not use word egress anymore.
> tks
>
> Andre
>
>
>
> Roy wrote:
> >>>Roy,
> >>> ''"''But this stability is probably not because my
> code is better but
> >
> > because
> >
> >>> I don't use egress shaping so the crash reasons still
> unknown.''"''
> >>>
> >>
> >>I need both ingress and egress traffic shaping, that's why I
> used the
> >>classic IMQ version.
> >
> >
> >
> > Egress shaping will crash original wersion even faster then
> mine,
> > they both can do this , but then both will likely crash
> > anyway you can do egress shaping on interface directly,
> > and input+forward on imq device.
> >
> > _______________________________________________
> > 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/
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-02-20 18:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 16:19 [LARTC] IMQ patch for iptables-1.2.9 and kernel 2.6.2 final ! The Codrinus
2004-02-19 18:28 ` Stef Coene
2004-02-19 19:18 ` The Codrinus
2004-02-20 0:15 ` Roy
2004-02-20 0:56 ` The Codrinus
2004-02-20 1:13 ` Roy
2004-02-20 11:45 ` Andre Correa
2004-02-20 17:16 ` Patrick McHardy
2004-02-20 18:21 ` Roy [this message]
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='005f01c3f7de$4e463450$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.