36fbedcbfc
In case of enabled packet forwarding mode, packets were forwarded in a reverse order because of LIFO behavior of the connection event list. The issue exposed only during high network traffic. Thus the event list started to grow that resulted in changing the order of packets inside of groups of several packets like the following: 3, 2, 1, 6, 5, 4, 8, 7 etc. Remarks concerning the connection event list implementation: * Now the queue (list) is FIFO as it should be. * The list is singly linked. * The list has a head pointer (inside of outer net_driver_s structure), and a tail pointer is added into outer net_driver_s structure. * The list item is devif_callback_s structure. It still has two pointers to two different list chains (*nxtconn and *nxtdev). * As before the first argument (*dev) of the list functions can be NULL, while the other argument (*list) is effective (not NULL). * An extra (*tail) argument is added to devif_callback_alloc() and devif_conn_callback_free() functions. * devif_callback_alloc() time complexity is O(1) (i.e. O(n) to fill the whole list). * devif_callback_free() time complexity is O(n) (i.e. O(n^2) to empty the whole list). * devif_conn_event() time complexity is O(n). |
||
|---|---|---|
| .. | ||
| Kconfig | ||
| Make.defs | ||
| bluetooth.h | ||
| bluetooth_callback.c | ||
| bluetooth_conn.c | ||
| bluetooth_container.c | ||
| bluetooth_finddev.c | ||
| bluetooth_initialize.c | ||
| bluetooth_input.c | ||
| bluetooth_poll.c | ||
| bluetooth_recvmsg.c | ||
| bluetooth_sendmsg.c | ||
| bluetooth_sockif.c | ||