 |
 |
I suppose that also means that SSI need not redispatch callbacks on another thread as well (it does so now), right? On Sat, 15 Jul 2017, xrootd-dev wrote: > You're right. It should work fine. Thanks for explaining and refreshing > my memory! > > On Sat, Jul 15, 2017, at 22:22, simonmichal wrote: >> I think the problem (in particular) was that some callbacks were executed >> within a thread that was holding the stream lock. Since now all the >> error/timeout callbacks are delegated to the thread-pool, this should be >> fixed by definition ;-) (the thread-pool worker threads are not holding >> any additional locks, right?). >> >> That said, fell free to point out which part of the patch is working you! >> ;-) >> >> -- >> You are receiving this because you are subscribed to this thread. >> Reply to this email directly or view it on GitHub: >> https://github.com/xrootd/xrootd/issues/257#issuecomment-315559850 >> >> ######################################################################## >> Use REPLY-ALL to reply to list >> >> To unsubscribe from the XROOTD-DEV list, click the following link: >> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1 > > > -- > You are receiving this because you commented. > Reply to this email directly or view it on GitHub: > https://github.com/xrootd/xrootd/issues/257#issuecomment-315564264 -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/257#issuecomment-315574301 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1