From: Marek Lindner <mareklindner@neomailbox.ch>
To: "Кирилл Луконин" <klukonin@gmail.com>
Cc: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [PATCH] batman-adv: Use wifi rx/tx as fallback throughput
Date: Thu, 27 Jun 2019 18:57:48 +0800 [thread overview]
Message-ID: <7822200.cGPG6thHbD@rousseau> (raw)
In-Reply-To: <CALYz8ypn2fQYCxbFDCbUmAgYHcHaxzPgGWkQPAhz2qxy3Qu-RA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
On Thursday, 27 June 2019 18:41:54 HKT Кирилл Луконин wrote:
> Mostly QCA988x was tested.
> Sorry, I lost my test results so I need to do it again.
> I have UBNT AC MESH, UBNT AP AC Lite and TP-Link RE450 in my lab.
It'd be great to see those numbers.
> Also, as I think, it's better to test UDP throughput, But I can test
> both TCP and UDP.
> This formula always show a result that close to UDP throughput. So,
> may be we can think about additional parameters/coefficients that
> depend on protocols or something else.
Why is UDP better ? The thinking behind comparing to TCP throughput is that
most applications use TCP and not UDP.
Cheers,
Marek
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-27 10:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 10:19 [PATCH] batman-adv: Use wifi rx/tx as fallback throughput René Treffer
2019-06-09 10:37 ` Sven Eckelmann
2019-06-09 11:40 ` Marek Lindner
2019-06-09 12:45 ` René Treffer
2019-06-10 3:31 ` Marek Lindner
2019-06-10 7:37 ` Кирилл Луконин
2019-06-12 6:39 ` Marek Lindner
2019-06-12 20:50 ` Кирилл Луконин
2019-06-25 8:26 ` Marek Lindner
2019-06-27 10:41 ` Кирилл Луконин
2019-06-27 10:57 ` Marek Lindner [this message]
2019-06-10 10:06 ` René Treffer
2019-08-11 12:50 ` Marek Lindner
[not found] ` <CALD2-cLnviLCav=Lui9T4Mzz1nnY93kN_0ypd-nhwFUhKNYRQg@mail.gmail.com>
2019-08-11 13:17 ` Marek Lindner
2019-06-09 10:41 ` Sven Eckelmann
2019-06-09 11:09 ` Sven Eckelmann
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=7822200.cGPG6thHbD@rousseau \
--to=mareklindner@neomailbox.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=klukonin@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;
as well as URLs for NNTP newsgroup(s).