From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 15D103B25D for ; Sat, 30 Jul 2016 09:48:47 -0400 (EDT) Received: by mail-pa0-x232.google.com with SMTP id iw10so39179304pac.2 for ; Sat, 30 Jul 2016 06:48:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fSg7K94pqcInVVfun3t3j1sSqBrpjJdXv909YGXz4YU=; b=Nyotj8VTZ9SBn/X/yfMxUzvYFObH4R2QadaQrBOdxTU5d9v+RRmU/lfbO0DsIoJdei TsWUUdot6m1Jiu4srFDGYvVilhMZUgPHOT1+rChA/qE+qBElNPGxnkkFx0uWITMnwU9J lJxZbeP7wGPUx3URB/+gdrNUfMJCOsfMCpijTEKyaJLtt4s9IMHq85jj2i9m7iEmTROy F/2U9Ai9JVLYiV4WdAhy1R3NC/t2giRYE3hQvaBNGdcLuVypDVjvuDlgEdh8UyldgYGQ jLCC4THamnEFdKJe7fX39saBIPhgG5zuCy4rt1z6lPibElZiQ4jNPegF5v7CKYx8P4LS Zlpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fSg7K94pqcInVVfun3t3j1sSqBrpjJdXv909YGXz4YU=; b=FlyE+X6ub04x098Esgnw0dY1hgw66cK+2tkNw0LAGMWySeRB/wLoumWszlHW8o3fNS wiBzOmrSDQKOFTlw/NfbX95AQ/bHsPvITdUoayTFmyijf+tor/atfzAWZsaryzpEGgsK jO5DuT9eYcEA6bOwjhT/pA/dQMdNf6EY6Fpeyf3MuMzdBorn9s9xnvESpGcRM6KUQNNn 5xpXHbJkQIxiMwBKShkkXUOa0mE/YAI600Os02mAQyMmFcX1kusoZFF2y7GdrDy40sHi 10xADuD0vN6off077e+gHXqDMbkRVXlDkliZVCOYgw/BjDzVC/Py2c+U3+Y3uvo8K7sS R+Kw== X-Gm-Message-State: AEkoousAgTHmOQ0YWM5U4l+Lr9SuaX2B3+ae9uMYl3NltCGjnWUn2zrCIf6KRPl8YlqgpLzMOMrDiTVZ6HUT8g== X-Received: by 10.66.194.198 with SMTP id hy6mr14904266pac.23.1469886527165; Sat, 30 Jul 2016 06:48:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.142.133 with HTTP; Sat, 30 Jul 2016 06:48:46 -0700 (PDT) In-Reply-To: References: <66C89432-6E70-422F-A638-7522BF233707@gmail.com> <35967373-D9F6-4C0C-8005-787DB8C7B1BB@gmx.de> <7ECE7E7A-0310-4DC4-8AC9-29B0F1F2E383@gmx.de> <4F22259A-17C8-4353-B34B-55D7E194D1EB@gmx.de> <43469614-F02B-4D9B-8D0E-14D0F4211CF1@gmail.com> <0B5FF17F-817F-4993-826D-DE55387D8D91@gmx.de> <001B301F-5F3D-4751-A252-ED67021B0BC2@gmx.de> From: Loganaden Velvindron Date: Sat, 30 Jul 2016 17:48:46 +0400 Message-ID: To: Mario Ferreira Cc: moeller0 , cake@lists.bufferbloat.net Content-Type: text/plain; charset=UTF-8 Subject: Re: [Cake] fq_codel on 3g network in Mauritius X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jul 2016 13:48:48 -0000 On Sat, Jul 30, 2016 at 5:04 PM, Mario Ferreira wrote: > You could also use a custom kernel that would allow you to add fq_codel/cake > then add custom rules to it. > CeroAndroid :) > I would advise a setup such as: AFWall to run scripts depending on whether > it's WiFi or Mobile (3G/4G). The script would be a simplified debloat.sh > just adding simple tc fq_codel/cake commands. I was thinking along the same line. However, my end goal would be to build a case for Android to consider shipping fq_codel instead of fifo_fast for android one. Instead of keeping the patches out of android one tree, at least we could try to make them accept it. > > I tried this before on the Samsung Galaxy Nexus back on 2013 [1] [2] with > AK_Kernel. I had interesting results though mixed ones. It was mostly due to > mobile data quality being awfully varied. Therefore, I wasn't knowledgeable > to find a good script setup that catered for all the moving parts. > Nonetheless, it improved my situation. I recommend it. > > I've been meaning to try this again using a modified Franco kernel [2] for > Huawei Nexus 6P. However, as with everyone else, Real Life(TM) has a > tendency to get in the way. :) I don't use custom ROMs. It would be a stock > Nexus ROM installation, SU root for scripts/tc and custom kernel for > fq_codel/cake kernels. > > We could try if people are interested. However, I can only be of help after > November. > I think that if I could get some kind of BQL/DQL into the mediatek driver, and convince the mediatek folks to take the patch by showing them the benefits, we could get a long way towards seeing an upcoming release of android with support for this. The nice thing is that it appears that the mediatek driver on the android repository is complete. > 1. > http://forum.xda-developers.com/galaxy-nexus/general/kernel-codel-kernel-modules-android-t2163790 > 2. https://github.com/lioux/ (Be kind, I know my github account looks like a > junior developer's sandbox :) :) > > On Sat, Jul 30, 2016 at 12:45 AM Loganaden Velvindron > wrote: >> >> I went further, and rooted the android phone. >> >> Then I set the txqueulen to 0 on ccimni0 and wlan0. >> >> Here are the results: >> https://www.dslreports.com/speedtest/4569339 >> https://www.dslreports.com/speedtest/4569379 >> >> >> Despite disabling the txqueuelen, The inbuilt TX/RX buffers are still >> pretty high: >> >> >> https://android.googlesource.com/kernel/mediatek/+/android-6.0.1_r0.100/drivers/misc/mediatek/dual_ccci/ccmni_net.c >> >> >> #define CCMNI_TX_QUEUE 1000 >> #define CCMNI_UART_OFFSET 2 >> >> So my idea is to reduce the size of the queues so that it's just >> enough for 21Mbit/s (down) , and 4Mbit/s (up), in the absence of BQL >> support. >> _______________________________________________ >> Cake mailing list >> Cake@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/cake > > -- > > Mario S F Ferreira - Brazil - "I guess this is a signature." > feature, n: a documented bug | bug, n: an undocumented feature