On Tue, 2025-05-13 at 19:36 +0200, Jan Hendrik Farr wrote: > > > > Hm. Yeah, I missed the second path that goes there in this case ... > > > > https://p.sipsolutions.net/0c145f72fdec3cf5.txt > > This work! > > Interestingly though, now the order is always: > 1. client commit > 2. AP commit > 3. client confirm > 4. AP confirm > > It is now only ~5.3 ms between AP commit and client confirm vs > ~21.2 ms before. > > Do you have an explanation why this patch would change the timing? Probably scheduling delay in the firmware. Before, to send the second frame, the client would have create a new schedule and airtime allocation in the firmware. Now it just keeps the old one so doesn't have to. > So this test doesn't proof that it would work with the order the other way > around. Maybe I should try making iwd sleep while generating the commit. I guess you could, right. johannes
