Skip to contentSkip to conversation

L2CAP Flush_Timeout Error

PATCH New Ajay 2 participants 5 messages Oct 2, 2012 – Oct 8, 2012

Subsystems (2)
lore
Share & tools
lore

Ajay

author
#0 lore raw

Hi,
Im currently working in an A2DP stuff, where i noticed an error.
Here i wanted to monitor the flushed packets due to timeout.

I used the l2test code for my testing purpose

On client side "l2test -R -S <bdadddr> "
and i set the flush timeout as 100 (opts.flush_to = 100)

But later when i print the getsockopt value of flush_to, it
was showing some default value (65532) harcoded at kernel side.

so how can i flush some packets in the sender side, without
enabling any retransmission and able to monitor the sequence number in the receiver side.

--
Thanks & regards

AJAY KV
8892753703

author
#2 lore raw
In reply to Andrei Emeltchenko
Quoted 10 lines · Andrei Emeltchenko
Quoted 9 lines · Ajay

Hi,
Im currently working in an A2DP stuff, where i noticed an error.
Here i wanted to monitor the flushed packets due to timeout.

I used the l2test code for my testing purpose

On client side "l2test -R -S <bdadddr> "
and i set the flush timeout as 100 (opts.flush_to = 100)

Quoted 8 lines
Quoted 2 lines

But later when i print the getsockopt value of flush_to, it
was showing some default value (65532) harcoded at kernel side.

Try the patch in this thread.

Best regards
Andrei Emeltchenko

Thanks for your patch , its working fine. Now even if i set the
flush_timeout = 5 , i couldnt able to see any packets missing at the receiver side . Here in the sender side im giving proper sequence number, and these same sequence is getting at the receiver side . i doubted even though its flushing , controller is doing some retransmission job...please help . My kernel is 2.6.39 , and im using BASIC MODE of transmission. so shall i change it to STEAMING MODE ????

Signature · 4 lines
 Thanks & regards

AJAY KV
8892753703
author
#3 lore raw
Quoted 12 lines · Ajay
Quoted 9 lines

Hi,
Im currently working in an A2DP stuff, where i noticed an error.
Here i wanted to monitor the flushed packets due to timeout.

I used the l2test code for my testing purpose

On client side "l2test -R -S <bdadddr> "
and i set the flush timeout as 100 (opts.flush_to = 100)

Quoted 8 lines
Quoted 2 lines

But later when i print the getsockopt value of flush_to, it
was showing some default value (65532) harcoded at kernel side.

Try the patch in this thread.

Best regards
Andrei Emeltchenko

Thanks for your patch , its working fine. Now even if i set the
flush_timeout = 5 , i couldnt able to see any packets missing at the receiver side . Here in the sender side im giving proper sequence number, and these same sequence is getting at the receiver side . i doubted even though its flushing , controller is doing some retransmission job...please help . My kernel is 2.6.39 , and im using BASIC MODE of transmission. so shall i change it to STEAMING MODE ????

Signature · 4 lines
 Thanks & regards

AJAY KV
8892753703
#4 lore raw

PATCH 1/1 Bluetooth: Allow to set flush timeout

In reply to Ajay

From: Andrei Emeltchenko <[email protected]>

---
 net/bluetooth/l2cap_sock.c |    1 +
 1 file changed, 1 insertion(+)
net/bluetooth/l2cap_sock.c +1 -0
index 0c05d7d..70578d8 100644
@@ -536,6 +536,7 @@ static int l2cap_sock_setsockopt_old(struct socket *sock, int optname, char __us
 		chan->fcs  = opts.fcs;
 		chan->max_tx = opts.max_tx;
 		chan->tx_win = opts.txwin_size;
+		chan->flush_to = opts.flush_to;
 		break;
 
 	case L2CAP_LM:
Signature · 1 line
1.7.9.5
#1 lore raw
In reply to Ajay
Quoted 11 lines · Ajay

Hi,
Im currently working in an A2DP stuff, where i noticed an error.
Here i wanted to monitor the flushed packets due to timeout.

I used the l2test code for my testing purpose

On client side "l2test -R -S <bdadddr> "
and i set the flush timeout as 100 (opts.flush_to = 100)

But later when i print the getsockopt value of flush_to, it
was showing some default value (65532) harcoded at kernel side.

Try the patch in this thread.

Best regards
Andrei Emeltchenko