[Mono-dev] TCP 3.0.1/2

[Rodrigo Kumpera]

I don't have anything but the current test case posted on this thread.

I can reproduce it easily on 64bits Ubuntu with epoll enabled but it worked
flawlessly for an hour with epoll disabled.

I think the right fix is to do take a similar approach of the poll backend
on how to notify the watcher thread of configuration changes.
Just send all changes over a pipe and let a single thread do it.




On Wed, Jan 23, 2013 at 10:15 AM, Andres G. Aragoneses <knocte at gmail.com>wrote:

>
> Hey Rodrigo,
>
> If you mention already the epoll backend as the place where the bug is,
> does that mean you have already a more isolated testcase than the one
> posted earlier in this thread? If yes, I might look into it, but I don't
> promise anything.
>
> Thanks
>
>
> On 21/01/13 19:27, Rodrigo Kumpera wrote:
>
>> Yes, it's the current suggested workaround until someone post a fix for
>> the epoll backend.
>>
>>
>> On Mon, Jan 21, 2013 at 10:10 AM, Roope Kangas <roope at grandcrugames.com
>> <mailto:roope at grandcrugames.**com <roope at grandcrugames.com>>> wrote:
>>
>>     Hi!
>>
>>     Whats the status of this issue?
>>
>>     Is the "best" way on mono to implement a server by writing it
>>     against the *Async API and then settings MONO_DISABLE_AIO=1
>>
>>     Seems odd?
>>
>>     --
>>     Roope
>>
>>     On Dec 7, 2012, at 6:44 PM, Rodrigo Kumpera <kumpera at gmail.com
>>     <mailto:kumpera at gmail.com>> wrote:
>>
>>      By the way, did you guys tried MONO_DISABLE_AIO=1 by any chance on
>>>     your tests? It solves the issue for me.
>>>
>>>
>>>     On Thu, Dec 6, 2012 at 3:46 AM, Greg Young
>>>     <gregoryyoung1 at gmail.com <mailto:gregoryyoung1 at gmail.**com<gregoryyoung1 at gmail.com>>>
>>> wrote:
>>>
>>>         We have code that shows the issue
>>>         https://github.com/ysw/mono-**socket-problem/tree/master/**
>>> SocketTest<https://github.com/ysw/mono-socket-problem/tree/master/SocketTest>
>>>
>>>         Greg
>>>
>>>         On Fri, Nov 30, 2012 at 4:10 PM, Rodrigo Kumpera
>>>         <kumpera at gmail.com <mailto:kumpera at gmail.com>> wrote:
>>>
>>>             Btw, I managed to find a linux bot that shows the io
>>>             callback issue.
>>>             The TP test works fine though.
>>>
>>>
>>>             On Fri, Nov 30, 2012 at 12:29 AM, Greg Young
>>>             <gregoryyoung1 at gmail.com <mailto:gregoryyoung1 at gmail.**com<gregoryyoung1 at gmail.com>
>>> >>
>>>
>>>             wrote:
>>>
>>>                 Thats already been provided (though its not hard to
>>>                 do). I will
>>>                 reupload a test that shows beahviour.
>>>
>>>
>>>
>>>
>>>
>>>         --
>>>         Le doute n'est pas une condition agréable, mais la certitude
>>>         est absurde.
>>>
>>>
>>>     ______________________________**_________________
>>>     Mono-devel-list mailing list
>>>     Mono-devel-list at lists.ximian.**com<Mono-devel-list at lists.ximian.com>
>>>     <mailto:Mono-devel-list at lists.**ximian.com<Mono-devel-list at lists.ximian.com>
>>> >
>>>     http://lists.ximian.com/**mailman/listinfo/mono-devel-**list<http://lists.ximian.com/mailman/listinfo/mono-devel-list>
>>>
>>
>>
>>
>>
>> ______________________________**_________________
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.**com <Mono-devel-list at lists.ximian.com>
>> http://lists.ximian.com/**mailman/listinfo/mono-devel-**list<http://lists.ximian.com/mailman/listinfo/mono-devel-list>
>>
>>
>
> ______________________________**_________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.**com <Mono-devel-list at lists.ximian.com>
> http://lists.ximian.com/**mailman/listinfo/mono-devel-**list<http://lists.ximian.com/mailman/listinfo/mono-devel-list>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20130123/b324a3c0/attachment.html>