public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] 11ac throughput on mesh links
Date: Mon, 01 Jan 2018 13:12:53 +0800	[thread overview]
Message-ID: <2542365.bvxhBZAykN@lafayette> (raw)
In-Reply-To: <CAL3ir7LUCHfyxegLn7qbx8cQ_H73V6AnTtBBN2eUPg7Wwn3j+A@mail.gmail.com>

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

On Sunday, December 31, 2017 8:41:03 AM HKT Daniel Ghansah wrote:
> Throughput: 13.61 MB/s (114.15 Mbps)
> is this inline with what everyone has seen. That data rate established is
> high however the throughput is very low

>         tx bitrate:     6.0 MBit/s

Is the tx bitrate field what you are wondering about (vs the measured speed) ?

This is a known bug caused by the QCA WiFi driver firmware blob. The exported
TX bitrate value is utterly bogus. Only QCA is in the position to fix that.

There have been attempts such as this one:
 https://github.com/torvalds/linux/commit/c1dd8016ae02557e4f3fcf7339865924d9357f76
Not sure this fix addresses your case. Sven might know.

Cheers,
Marek

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2018-01-01  5:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-31 13:41 [B.A.T.M.A.N.] 11ac throughput on mesh links Daniel Ghansah
2017-12-31 19:54 ` dan
     [not found] ` <9028hd66ebd1b22pauq0on7r.1514743576208@email.android.com>
2017-12-31 23:17   ` Daniel Ghansah
2018-01-01  5:12 ` Marek Lindner [this message]
2018-01-01  9:13   ` Sven Eckelmann
2018-01-01 16:33     ` Daniel Ghansah
2018-01-01 17:06       ` Marek Lindner

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

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

  git send-email \
    --in-reply-to=2542365.bvxhBZAykN@lafayette \
    --to=mareklindner@neomailbox.ch \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /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