From: dpreed@reed.com
To: "Maciej Soltysiak" <maciej@soltysiak.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Google working on experimental 3.8 Linux kernel for Android
Date: Thu, 28 Feb 2013 13:57:25 -0500 (EST) [thread overview]
Message-ID: <1362077845.101114942@apps.rackspace.com> (raw)
In-Reply-To: <CAMZR1YCh0TvRcX864pwkVY1KJmGPrO_C2+yN9if32z0yzM-=_Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
Doesn't fq_codel need an estimate of link capacity? Where will it get that from the 4G or 3G uplink?
-----Original Message-----
From: "Maciej Soltysiak" <maciej@soltysiak.com>
Sent: Thursday, February 28, 2013 1:03pm
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Google working on experimental 3.8 Linux kernel for Android
Hiya,
Looks like Google's experimenting with 3.8 for Android: [https://android.googlesource.com/kernel/common/+/experimental/android-3.8] https://android.googlesource.com/kernel/common/+/experimental/android-3.8
Sounds great if this means they will utilize fq_codel, TFO, BQL, etc.
Anyway my nexus 7 says it has 3.1.10 and this 3.8 will probably go to Android 5.0 so I hope Nexus 7 will get it too some day or at least 3.3+
Phoronix coverage: [http://www.phoronix.com/scan.php?page=news_item&px=MTMxMzc] http://www.phoronix.com/scan.php?page=news_item&px=MTMxMzc
Their 3.8 changelog: [https://android.googlesource.com/kernel/common/+log/experimental/android-3.8] https://android.googlesource.com/kernel/common/+log/experimental/android-3.8
Regards,
Maciej
[-- Attachment #2: Type: text/html, Size: 1551 bytes --]
next prev parent reply other threads:[~2013-02-28 18:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 18:03 Maciej Soltysiak
2013-02-28 18:57 ` dpreed [this message]
2013-02-28 19:08 ` Dave Taht
2013-02-28 20:03 ` Jim Gettys
2013-02-28 20:58 ` dpreed
2013-02-28 21:02 ` Jim Gettys
2013-02-28 21:10 ` dpreed
2013-03-01 8:00 ` Ketan Kulkarni
2013-03-01 15:40 ` dpreed
2013-03-01 16:09 ` Jim Gettys
2013-03-01 16:27 ` dpreed
2013-03-02 3:39 ` Ketan Kulkarni
2013-03-02 13:27 ` William Allen Simpson
2013-03-02 14:20 ` dpreed
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1362077845.101114942@apps.rackspace.com \
--to=dpreed@reed.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=maciej@soltysiak.com \
/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