From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:47816) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UFjOp-0003SB-OK for qemu-devel@nongnu.org; Wed, 13 Mar 2013 06:59:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UFjOi-0000KX-1S for qemu-devel@nongnu.org; Wed, 13 Mar 2013 06:59:11 -0400 Received: from mx1.redhat.com ([209.132.183.28]:7533) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UFjOh-0000KI-Q7 for qemu-devel@nongnu.org; Wed, 13 Mar 2013 06:59:03 -0400 Message-ID: <51405BEA.6080109@redhat.com> Date: Wed, 13 Mar 2013 11:58:50 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1363154346-14827-1-git-send-email-qemulist@gmail.com> In-Reply-To: <1363154346-14827-1-git-send-email-qemulist@gmail.com> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH 0/2] port network layer onto glib List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Liu Ping Fan Cc: mdroth , Stefan Hajnoczi , qemu-devel@nongnu.org, Anthony Liguori , "Michael S. Tsirkin" Il 13/03/2013 06:59, Liu Ping Fan ha scritto: > These series aim to port network backend onto glib, and > prepare for moving towards making network layer mutlit-thread. > The brief of the whole aim and plan is documented on > http://wiki.qemu.org/Features/network_reentrant > > In these series, attach each NetClientState with a GSource > At the first, I use AioContext instead of GSource, but after discussion, > I think with GSource, we can integrated with glib more closely. Integrating with glib by itself is pointless. What is the *benefit*? We have a pretty good idea of how to make multithreaded device models using AioContext, since we are using it for the block layer and virtio-blk dataplane. Doing the same work twice, on two different frameworks, doesn't seem like a very good idea. Paolo