From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:57547) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QxaQa-0007AC-Vy for qemu-devel@nongnu.org; Sun, 28 Aug 2011 04:09:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QxaQZ-000403-UK for qemu-devel@nongnu.org; Sun, 28 Aug 2011 04:09:12 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41907) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QxaQZ-0003zw-K7 for qemu-devel@nongnu.org; Sun, 28 Aug 2011 04:09:11 -0400 Message-ID: <4E59F79F.1030504@redhat.com> Date: Sun, 28 Aug 2011 11:09:03 +0300 From: Avi Kivity MIME-Version: 1.0 References: <1313294689-21572-1-git-send-email-avi@redhat.com> <4E5291DF.1070603@siemens.com> <4E539FA9.3010507@codemonkey.ws> <4E53A4E4.1090807@siemens.com> <4E53B2D8.7080608@codemonkey.ws> <4E53B4C9.3070906@siemens.com> In-Reply-To: <4E53B4C9.3070906@siemens.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v2] posix-aio-compat: fix latency issues List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Kevin Wolf , Stefan Hajnoczi , "kvm@vger.kernel.org" , "qemu-devel@nongnu.org" On 08/23/2011 05:10 PM, Jan Kiszka wrote: > On 2011-08-23 16:02, Anthony Liguori wrote: > > On 08/23/2011 08:02 AM, Jan Kiszka wrote: > >> On 2011-08-23 14:40, Anthony Liguori wrote: > >>> You should be able to just use an eventfd or pipe. > >>> > >>> Better yet, we should look at using GThreadPool to replace posix-aio-compat. > >> > >> When interacting with the thread pool is part of some time-critical path > >> (easily possible with a real-time Linux guest), general-purpose > >> implementations like what glib offers are typically out of the game. > >> They do not provide sufficient customizability, specifically control > >> over their internal synchronization and allocation policies. That > >> applies to the other rather primitive glib threading and locking > >> services as well. > > > > We can certainly enhance glib. glib is a cross platform library. I > > Do you want to carry forked glib bits in QEMU? We can make real-time depend on a newer glib version. > > > don't see a compelling reason to invent a new cross platform library > > just for QEMU especially if the justification is future features, not > > current features. > > Tweaking affinity of aio threads is already a current requirement. > > And we already have a working threading and locking system. One that is > growing beyond glib's level of support quickly (think of RCU). > glib will have to support RCU as well. But for this topic, I agree with you for now. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.