Hi
On Fri, Mar 23, 2018 at 6:50 AM, Peter Xu wrote:
> On Thu, Mar 22, 2018 at 01:00:19PM +0100, Marc-André Lureau wrote:
>> Hi
>>
>> On Fri, Mar 9, 2018 at 10:00 AM, Peter Xu wrote:
>> > For those monitors who have enabled IO thread, we'll offload the
>> > responding procedure into IO thread. T
On Thu, Mar 22, 2018 at 01:00:19PM +0100, Marc-André Lureau wrote:
> Hi
>
> On Fri, Mar 9, 2018 at 10:00 AM, Peter Xu wrote:
> > For those monitors who have enabled IO thread, we'll offload the
> > responding procedure into IO thread. The main reason is that chardev is
> > not thread safe, and w
Hi
On Fri, Mar 9, 2018 at 10:00 AM, Peter Xu wrote:
> For those monitors who have enabled IO thread, we'll offload the
> responding procedure into IO thread. The main reason is that chardev is
> not thread safe, and we need to do all the read/write IOs in the same
> thread. For use_io_thr=true
For those monitors who have enabled IO thread, we'll offload the
responding procedure into IO thread. The main reason is that chardev is
not thread safe, and we need to do all the read/write IOs in the same
thread. For use_io_thr=true monitors, that thread is the IO thread.
We do this isolation
