On Fri, 2019-10-18 at 12:15 +0200, Toke Høiland-Jørgensen wrote: > However, there's a nice juicy 'u16 ack_frame_id' at the start of > ieee80211_tx_info. Could we potentially use that? We could use the top > bit as a disambiguation flag; I think we're fine with 15 bits for the TX > time itself (a single packet won't exceed 8ms or TX time), so if we can > live with 15 bits of ACK frame ID space, that could be a way forward? I was going to say that should work as we only ever have a handful of ACK frame IDs, but ... you still need the airtime even for a frame that userspace wants to know the ACK status of, no? We could pull the ack_frame_id out-of-line using the skb extensions framework, but I'm not sure we should allocate one of the possible 8 extension IDs for that either ... What we really should do is convert all (relevant) drivers to use rate tables instead of having all the rates in the TX info, then we'd get a lot of space, but that's a lot of work ... johannes
