b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH] batman-adv: Use wifi rx/tx as fallback throughput
Date: Sun, 11 Aug 2019 20:50:38 +0800	[thread overview]
Message-ID: <2541950.y14E6QPJ2z@rousseau> (raw)
In-Reply-To: <8c0c76dc-5c6b-da84-8e11-700222641db8@measite.de>

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

On Monday, 10 June 2019 18:06:23 HKT René Treffer wrote:
> > I also don't quite understand what the '!!!' thing is trying to indicate.
> > What is being compared ? But it may be due to my misunderstandings above.
>
> I haven't done an actual throughput test, and I would expect the outputs
> of my heuristic to be worse.
> So I wanted to give slightly lower values than the expected throughput.
> 
> The other way to think about it: if you were to replace the
> expected_throughput input where would you over-estimate the link quality
> now?

Sorry, I don't follow that train of thought. Due to the lack of numbers 
comparing the magic formula (tx /3) with actual throughput we (Antonio and I) 
ran a few tests on ath10k devices using your patch. Surprising to us, this 
approach worked quite well. 

I will re-post your patch as RFC to encourage others to test the resulting 
B.A.T.M.A.N. V routing decisions. If you happen to have tested more on your 
end, please share your results.

Also, why considering rx on top of tx still isn't clear. Could you explain 
some more ?

Thanks,
Marek



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

  reply	other threads:[~2019-08-11 12:50 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
2019-06-10 10:06         ` René Treffer
2019-08-11 12:50           ` Marek Lindner [this message]
     [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=2541950.y14E6QPJ2z@rousseau \
    --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;
as well as URLs for NNTP newsgroup(s).