From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:60793)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <famz@redhat.com>) id 1ZaKsi-0000z7-Hv
	for qemu-devel@nongnu.org; Fri, 11 Sep 2015 05:44:33 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <famz@redhat.com>) id 1ZaKsh-0006EG-LL
	for qemu-devel@nongnu.org; Fri, 11 Sep 2015 05:44:32 -0400
Date: Fri, 11 Sep 2015 17:44:25 +0800
From: Fam Zheng <famz@redhat.com>
Message-ID: <20150911094425.GA9241@ad.nay.redhat.com>
References: <1438144934-23619-12-git-send-email-famz@redhat.com>
	<55B882C1.8070500@redhat.com>
	<20150729105725.GA10376@ad.nay.redhat.com>
	<55B8B2C3.9050307@redhat.com>
	<20150729115333.GA15022@ad.nay.redhat.com>
	<55B8C12D.2070105@redhat.com>
	<20150909032205.GA10922@ad.nay.redhat.com>
	<55F28D99.5060908@redhat.com>
	<20150911091433.GA6759@ad.nay.redhat.com>
	<w518u8d47sl.fsf@maestria.local.igalia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <w518u8d47sl.fsf@maestria.local.igalia.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v2 11/11] block: Only poll
 block layer fds in bdrv_aio_poll
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Alberto Garcia <berto@igalia.com>
Cc: kwolf@redhat.com, Paolo Bonzini <pbonzini@redhat.com>, stefanha@redhat.com, qemu-devel@nongnu.org, qemu-block@nongnu.org

On Fri, 09/11 11:36, Alberto Garcia wrote:
> On Fri 11 Sep 2015 11:14:33 AM CEST, Fam Zheng <famz@redhat.com> wrote:
> 
> >> > Another advantage for bdrv_aio_poll() is, in main loop we will not
> >> > need a separate AioContext in changes like:
> >> > 
> >> > http://patchwork.ozlabs.org/patch/514968/
> >> > 
> >> > Because nested aio_poll will automatically be limited to only
> >> > process block layer events. My idea is to eventually let main loop
> >> > use aio_poll
> >> 
> >> That would be a step back.  Using GSource is useful because it lets
> >> you integrate libraries such as GTK+.
> >
> > Can we move GTK to a separate GSource thread?
> 
> I think that GTK should always run in the main thread, or at least the
> one running the default main loop / GMainContext.

Yeah it's basically GMainContext staying in the main thread and
block/net/chardev I/O put in a new AioContext thread.

Fam