Re: [tipc-discussion] [PATCH net v1 3/3] tipc: wakeup sleeping users at disconnect

Acked-by: jon > -Original Message- > From: Parthasarathy Bhuvaragan > Sent: Tuesday, 04 October, 2016 08:29 > To: tipc-discussion@lists.sourceforge.net; Jon Maloy ; > ma...@donjonn.com; Ying Xue > Subject: [PATCH net v1 3/3] tipc: wakeup

Re: [tipc-discussion] [PATCH net v1 2/3] tipc: return early for non-blocking sockets at link congestion

> -Original Message- > From: Parthasarathy Bhuvaragan > Sent: Tuesday, 04 October, 2016 08:29 > To: tipc-discussion@lists.sourceforge.net; Jon Maloy ; > ma...@donjonn.com; Ying Xue > Subject: [PATCH net v1 2/3] tipc: return early for

[tipc-discussion] [PATCH net v1 1/3] tipc: fix socket wakeup when the transmit queue is empty

Until now, in tipc_link_rcv() the sockets are woken only when we were able to release a frame from the link's transmit queue. However link_prepare_wakeup(), wakes only as many users as permitted by the current link window and the rest of the users are woken the next time a frame is released. In

[tipc-discussion] [PATCH net v1 2/3] tipc: return early for non-blocking sockets at link congestion

Until now, in stream/mcast send() we pass the message to the link layer even when the link is congested and add the socket to the link's wakeup queue. This is unnecessary for non-blocking sockets. If a socket is set to non-blocking and sends multicast with zero back off time while receiving