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, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/xrootd/xrootd","title":"xrootd/xrootd","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@abh3 in #257: I suppose that also means that SSI need not redispatch callbacks on \nanother thread as well (it does so now), right?\n\nOn Sat, 15 Jul 2017, xrootd-dev wrote:\n\n\u003e You're right. It should work fine. Thanks for explaining and refreshing\n\u003e my memory!\n\u003e\n\u003e On Sat, Jul 15, 2017, at 22:22, simonmichal wrote:\n\u003e\u003e I think the problem (in particular) was that some callbacks were executed\n\u003e\u003e within a thread that was holding the stream lock. Since now all the\n\u003e\u003e error/timeout callbacks are delegated to the thread-pool, this should be\n\u003e\u003e fixed by definition ;-) (the thread-pool worker threads are not holding\n\u003e\u003e any additional locks, right?).\n\u003e\u003e\n\u003e\u003e That said, fell free to point out which part of the patch is working you!\n\u003e\u003e ;-)\n\u003e\u003e\n\u003e\u003e --\n\u003e\u003e You are receiving this because you are subscribed to this thread.\n\u003e\u003e Reply to this email directly or view it on GitHub:\n\u003e\u003e https://github.com/xrootd/xrootd/issues/257#issuecomment-315559850\n\u003e\u003e\n\u003e\u003e ########################################################################\n\u003e\u003e Use REPLY-ALL to reply to list\n\u003e\u003e\n\u003e\u003e To unsubscribe from the XROOTD-DEV list, click the following link:\n\u003e\u003e https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV\u0026A=1\n\u003e\n\u003e\n\u003e -- \n\u003e You are receiving this because you commented.\n\u003e Reply to this email directly or view it on GitHub:\n\u003e https://github.com/xrootd/xrootd/issues/257#issuecomment-315564264\n"}],"action":{"name":"View Issue","url":"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
