Adding "no-ack" flag to the radiotap flags

Adding "no-ack" flag to the radiotap flags

[Michael Buesch]

Hi.

Currently, there's no way to define whether the hardware
should wait for an ACK for an injected frame or not.
This can be a performance bottleneck, as the hardware will
try to retransmit until it receives an ACK.

I suggest adding
#define IEEE80211_RADIOTAP_F_NOACK	0x40
so an application can define that it is not interested in
an ACK for the frame and the card should not bother retrying until
it received one.
When this flag is not set, the standard rules apply.

I don't see a use-case for overriding these rules to always
_expect_ an ACK, so I think a one-bit flag is OK.

-- 
Greetings Michael.

Re: Adding "no-ack" flag to the radiotap flags

[Johannes Berg]

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


> I suggest adding
> #define IEEE80211_RADIOTAP_F_NOACK	0x40
> so an application can define that it is not interested in
> an ACK for the frame and the card should not bother retrying until
> it received one.
> When this flag is not set, the standard rules apply.
> 
> I don't see a use-case for overriding these rules to always
> _expect_ an ACK, so I think a one-bit flag is OK.

I'd add it to the TX flags instead, especially seeing that the bit 0x40
is already assigned there in some BSDs.

johannes

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