All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] NEW imq driver
Date: Tue, 27 Jan 2004 08:42:05 +0000	[thread overview]
Message-ID: <4016245D.7070101@dsl.pipex.com> (raw)
In-Reply-To: <002a01c3e466$bb7f8700$030aa8c0@t>

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
> generated packets
> if you try to drop them you will be sorry, because kernel will resend then
> together with new ones
> of cource policer will drop them too, but linux kernel keeps resending then
> thus increasing rate progresively.
> 
> 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 similar problem  even if driver itself have no leaks kernel
> consumes all resousces on resnending droped packets so that computer stops
> responding
> 
> 
> for now I dont have good idea how to fix it so I will try to avoid localy
> generated trafic
> so it will me possible to shape ingress and forward, egress will be left for
> real device.
> maybe later I will find how fix that

Which queue do you use to drop the packets?

Andy.

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

  parent reply	other threads:[~2004-01-27  8:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-26 23:47 [LARTC] NEW imq driver Roy
2004-01-27  3:56 ` rubens
2004-01-27  4:33 ` Michael Renzmann
2004-01-27  4:42 ` Roy
2004-01-27  8:42 ` Andy Furniss [this message]
2004-01-27 14:28 ` Philip Thiem

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=4016245D.7070101@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.com \
    --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.