From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-qk0-x22d.google.com ([2607:f8b0:400d:c09::22d]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1awztI-0006Ah-EG for ath10k@lists.infradead.org; Sun, 01 May 2016 22:31:04 +0000 Received: by mail-qk0-x22d.google.com with SMTP id q76so59072868qke.2 for ; Sun, 01 May 2016 15:30:44 -0700 (PDT) Message-ID: <1462141840.5535.223.camel@edumazet-glaptop3.roam.corp.google.com> Subject: Re: [Codel] fq_codel_drop vs a udp flood From: Eric Dumazet Date: Sun, 01 May 2016 15:30:40 -0700 In-Reply-To: References: <1462125592.5535.194.camel@edumazet-glaptop3.roam.corp.google.com> Mime-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Dave Taht Cc: make-wifi-fast@lists.bufferbloat.net, "codel@lists.bufferbloat.net" , ath10k On Sun, 2016-05-01 at 11:26 -0700, Dave Taht wrote: > On Sun, May 1, 2016 at 10:59 AM, Eric Dumazet wrote: > > > > Well, just _kill_ the offender, instead of trying to be gentle. > > I like it. :) Killing off a malfunctioning program flooding the local > network interface (intentionally or unintentionally) seems like a > useful idea. > .. > Killing the bad program, and dropping all of the fattest flow strike > me as two patches.[1] What I meant by 'killing' was to drop more than one packet from this fat flow, not actually killing a task. I will submit an official patch, dropping 50% of the fat flow backlog, and a configurable cap of 64 packets to somewhat control max ->enqueue() latency. _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k