Re: [PATCH 4/5] Bluetooth: Don't send RNR immediately when entering local busy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Szymon,

> There is no need to send RNR immediately when entring local busy.
> Also upper layer might clear local busy condition before ack timer
> expires saving few cycles for sending RNR.
> 
> This also prevents sending two RNRs in some cases where sending one
> would be enough i.e received N I-frame can trigger local busy
> (sending RNR acking up to N-1 I-frame) and later sending ack (RNR
> acking up to N I-frame).

exactly like this please.

> Signed-off-by: Szymon Janc <szymon.janc@xxxxxxxxx>
> ---
>  net/bluetooth/l2cap_core.c |   15 +++++----------
>  1 files changed, 5 insertions(+), 10 deletions(-)

It does not make sense without the previous patches resend, but this
patch is fine with me.

Regards

Marcel


--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux