From: Jonathan Morton <chromatix99@gmail.com>
To: Mario Ferreira <liouxbsd@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Testing fq_codel on Android Galaxy Nexus AK kernel
Date: Tue, 26 Feb 2013 20:27:59 +0200 [thread overview]
Message-ID: <CAJq5cE2wc4hg7i8QAWwaxoi_BUs386SpNTYgQqvB24dbi8+S6A@mail.gmail.com> (raw)
In-Reply-To: <CAH44DxbBjqv77V-QDGeg+p-1pbZtBQa-BFt0wLTgSNXKXZ1vbg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]
Since the phone only has control of the bottleneck in the upload direction,
a browse + upload or ping + upload or VoIP + upload test would be
appropriate. It's important to control the link speed as much as possible
to be the same for equivalent tests, and to try several different network
conditions.
Tests involving heavy downlink traffic would measure bloat at the cell
tower, or at the ISP or access point for wifi tests.
- Jonathan Morton
On Feb 26, 2013 7:58 PM, "Mario Ferreira" <liouxbsd@gmail.com> wrote:
> Hi,
>
> After a small exchange, AK kernel developer has added fq_codel to his
> Galaxy Nexus kernel distribution.
>
> http://forum.xda-developers.com/showthread.php?t=2163790
>
> Now, he would like to know how to benchmark it to see the advantages. :)
>
> I know basic tests for desktop: mtr, netalyzr.icsi.berkeley.edu and
> download + browsing..
>
> What do you suggest for a wireless only setup such as Android Phone?
>
> Best regards,
> Mário Sérgio
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
>
[-- Attachment #2: Type: text/html, Size: 1799 bytes --]
next prev parent reply other threads:[~2013-02-26 18:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH44Dxbt+fixeLHwmA7QnndhhUbAjUEORxAsfb5LarUD7a3ZMw@mail.gmail.com>
2013-02-26 17:40 ` Mario Ferreira
2013-02-26 18:27 ` Jonathan Morton [this message]
2013-02-26 18:48 ` Eric Dumazet
2013-02-26 19:25 ` Simon Barber
2013-02-26 22:25 ` Dave Taht
2013-02-28 6:08 ` Mário Sérgio Fujikawa Ferreira
2013-03-10 1:21 ` Mário Sérgio Fujikawa Ferreira
2013-03-10 1:26 ` Mário Sérgio Fujikawa Ferreira
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJq5cE2wc4hg7i8QAWwaxoi_BUs386SpNTYgQqvB24dbi8+S6A@mail.gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=liouxbsd@gmail.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