Re: [PATCH RFC 2/2] batman-adv: Better half duplex penalty estimation

2023-10-18 Thread Nicolas Escande
On Wed Oct 18, 2023 at 9:58 PM CEST, Remi Pommarel wrote: > [...] > > > > Also, this seems to assume that time slices are divided equally. > > That's probably only be true for WiFi drivers that have airtime > > fairness changes integrated? So only recent versions of mt76, > > ath9k and ath10k?

Re: [PATCH RFC 2/2] batman-adv: Better half duplex penalty estimation

2023-10-18 Thread Remi Pommarel
On Sat, Oct 14, 2023 at 07:10:28AM +0200, Linus Lüssing wrote: > Hi, > > Thanks for taking your time to look into this and the detailed > explanations! > > Generally, the issues both patches try to address make sense to me. > > > On Thu, Sep 28, 2023 at 02:39:36PM +0200, Remi Pommarel wrote: >

Re: [PATCH RFC 2/2] batman-adv: Better half duplex penalty estimation

2023-10-14 Thread Linus Lüssing
On Thu, Sep 28, 2023 at 02:39:36PM +0200, Remi Pommarel wrote: > diff --git a/net/batman-adv/bat_v_ogm.c b/net/batman-adv/bat_v_ogm.c > index 27597f4cdf3e..9b7d4de182d0 100644 > --- a/net/batman-adv/bat_v_ogm.c > +++ b/net/batman-adv/bat_v_ogm.c > @@ -866,10 +866,12 @@ static u32

Re: [PATCH RFC 2/2] batman-adv: Better half duplex penalty estimation

2023-10-14 Thread Linus Lüssing
On Sat, Oct 14, 2023 at 07:10:28AM +0200, Linus Lüssing wrote: > In the following scenario: > > +---+ ch.1 +---+ ch.2 +---+ ch.2 +---+ > | Orig0 | <- | Orig1 | <-- | Orig2 | <-- | Orig3 | > +---+ 300 +---+ 3 +---+110 +---+ >

Re: [PATCH RFC 2/2] batman-adv: Better half duplex penalty estimation

2023-10-13 Thread Linus Lüssing
Hi, Thanks for taking your time to look into this and the detailed explanations! Generally, the issues both patches try to address make sense to me. On Thu, Sep 28, 2023 at 02:39:36PM +0200, Remi Pommarel wrote: > Let's consider the below topology [...] > However the following formula seems to