From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Furniss Date: Tue, 27 Jan 2004 08:42:05 +0000 Subject: Re: [LARTC] NEW imq driver Message-Id: <4016245D.7070101@dsl.pipex.com> List-Id: References: <002a01c3e466$bb7f8700$030aa8c0@t> In-Reply-To: <002a01c3e466$bb7f8700$030aa8c0@t> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org 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/