On Wed, 11/08 15:31, Peter Xu wrote:
> On Tue, Nov 07, 2017 at 03:57:08PM +0800, Fam Zheng wrote:
> > On Mon, 11/06 17:46, Peter Xu wrote:
> > > @@ -4294,6 +4366,11 @@ static GMainContext *monitor_io_context_get(void)
> > > return iothread_get_g_main_context(mon_global.mon_iothread);
> > > }
On Tue, Nov 07, 2017 at 03:57:08PM +0800, Fam Zheng wrote:
> On Mon, 11/06 17:46, Peter Xu wrote:
> > @@ -4294,6 +4366,11 @@ static GMainContext *monitor_io_context_get(void)
> > return iothread_get_g_main_context(mon_global.mon_iothread);
> > }
> >
> > +static AioContext *monitor_aio_conte
On Mon, 11/06 17:46, Peter Xu wrote:
> @@ -4294,6 +4366,11 @@ static GMainContext *monitor_io_context_get(void)
> return iothread_get_g_main_context(mon_global.mon_iothread);
> }
>
> +static AioContext *monitor_aio_context_get(void)
> +{
> +return iothread_get_aio_context(mon_global.mon
For those monitors who has 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 i
