Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Mario Ferreira <liouxbsd@gmail.com>
To: Loganaden Velvindron <loganaden@gmail.com>
Cc: moeller0 <moeller0@gmx.de>, cake@lists.bufferbloat.net
Subject: Re: [Cake] fq_codel on 3g network in Mauritius
Date: Sat, 30 Jul 2016 14:07:30 +0000	[thread overview]
Message-ID: <CAH44DxbL8NQ9sETJHEwLoj=j0yy0WH6Xn1zn-OCWmy7AeuVffw@mail.gmail.com> (raw)
In-Reply-To: <CAOp4FwTkvOsLoKqbYY1fFAKH12pzE=7BicT_JxMQAtNkrZkk8Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2973 bytes --]

On Sat, Jul 30, 2016 at 10:48 AM Loganaden Velvindron <loganaden@gmail.com>
wrote:

> On Sat, Jul 30, 2016 at 5:04 PM, Mario Ferreira <liouxbsd@gmail.com>
> wrote:
> > You could also use a custom kernel that would allow you to add
> fq_codel/cake
> > then add custom rules to it.
> >
> CeroAndroid :)
>

  Nothing so grand. As in all things software, simpler/smaller/faster is
better (usually in that order). There are TOO many voices to interfere.


> > 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.
>

  My experience has been that you FIRST make a proof of concept. Get it
working, write the instructions, make it baby proof to code merge, etc.
THEN, you try to convince them to accept it.

  Franco kernel or any other custom kernel follows the official Android
git. We need to get it out there so that it gets attention. David Taht et
al have been working for YEARS on getting people to notice something that
has PHYSICAL verifiable proof = facts. It's a
technical/political/financial/faith/crazy issue. No intention to offend
anyone.


> > 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.


  I am all for it. Keep us posted. :) A lot of folks here have experience
on getting GOOD/NECESSARY/PROVED things going when everyone else disagrees.
Reach out. We can all benefit from it.
-- 

Mario S F Ferreira - Brazil - "I guess this is a signature."
feature, n: a documented bug | bug, n: an undocumented feature

[-- Attachment #2: Type: text/html, Size: 4002 bytes --]

  reply	other threads:[~2016-07-30 14:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19  4:29 Loganaden Velvindron
2016-07-19  8:09 ` Jonathan Morton
2016-07-19 10:16   ` moeller0
     [not found]     ` <CAOp4FwQs9-PF=V5zDDMVj_38qmziKkeZECTyX1e8EfChtGm8bA@mail.gmail.com>
     [not found]       ` <7ECE7E7A-0310-4DC4-8AC9-29B0F1F2E383@gmx.de>
2016-07-23 18:36         ` Loganaden Velvindron
2016-07-23 18:59           ` Loganaden Velvindron
2016-07-24  5:53             ` Loganaden Velvindron
2016-07-24  6:12               ` Loganaden Velvindron
2016-07-24  7:03                 ` Loganaden Velvindron
2016-07-24  8:27                   ` moeller0
2016-07-24  8:43                     ` Loganaden Velvindron
2016-07-24 10:53               ` moeller0
2016-07-24 11:28                 ` Jonathan Morton
2016-07-24 14:40                   ` moeller0
2016-07-24 16:18                     ` Jonathan Morton
2016-07-24 17:13                     ` Loganaden Velvindron
2016-07-24 17:21                       ` moeller0
2016-07-24 19:43                         ` Loganaden Velvindron
2016-07-25  4:13                           ` Loganaden Velvindron
2016-07-26 21:10                             ` Loganaden Velvindron
2016-07-30  3:45                               ` Loganaden Velvindron
2016-07-30 13:04                                 ` Mario Ferreira
2016-07-30 13:48                                   ` Loganaden Velvindron
2016-07-30 14:07                                     ` Mario Ferreira [this message]
2016-08-03 18:52                               ` Loganaden Velvindron
2016-08-03 19:48                                 ` David Lang
2016-07-19 17:13   ` Loganaden Velvindron

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

  List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH44DxbL8NQ9sETJHEwLoj=j0yy0WH6Xn1zn-OCWmy7AeuVffw@mail.gmail.com' \
    --to=liouxbsd@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=loganaden@gmail.com \
    --cc=moeller0@gmx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox