Could you provide me the exact code change for rescheduling, so I don't want to make any mistake.
Also, could I still apply the patch, "tipc: block BH in TCP callbacks" ? On Tue, May 31, 2016 at 12:03 PM, Erik Hugne <erik.hu...@gmail.com> wrote: > > On May 31, 2016 17:34, "GUNA" <gbala...@gmail.com> wrote: >> >> Which Erik's patch you are talking about? >> Is this one, "tipc: fix timer handling when socket is owned" ? > > I think he was referring to my earlier suggestion to reschedule the timer if > the socket is owned by user when it fires. > > The patch i sent yesterday tries to solve it slightly different. Instead of > rescheduling the timer, we set a flag and act on that when the sock is > released by user. > > //E ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ tipc-discussion mailing list tipc-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tipc-discussion
