From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51711) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vlzhi-000295-NS for qemu-devel@nongnu.org; Thu, 28 Nov 2013 06:24:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vlzhb-0006dt-CJ for qemu-devel@nongnu.org; Thu, 28 Nov 2013 06:24:18 -0500 Received: from mail-we0-f179.google.com ([74.125.82.179]:43975) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vlzhb-0006dk-6F for qemu-devel@nongnu.org; Thu, 28 Nov 2013 06:24:11 -0500 Received: by mail-we0-f179.google.com with SMTP id q59so8145021wes.10 for ; Thu, 28 Nov 2013 03:24:10 -0800 (PST) Date: Thu, 28 Nov 2013 13:23:48 +0200 From: Gleb Natapov Message-ID: <20131128112348.GF5822@minantech.com> References: <5294BC3B.6070902@redhat.com> <5297050E.6000700@redhat.com> <20131128091903.GA4609@kernel.org> <5297118C.3050104@cloudius-systems.com> <529712A1.8090207@redhat.com> <5297181B.3090109@cloudius-systems.com> <52971D86.60601@redhat.com> <20131128110915.GD5822@minantech.com> <529724B0.80405@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <529724B0.80405@redhat.com> Subject: Re: [Qemu-devel] [RFC] create a single workqueue for each vm to update vm irq routing table List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Avi Kivity , "Huangweidong (C)" , Gleb Natapov , KVM , "Michael S. Tsirkin" , "Zhanghaoyu (A)" , Luonengjun , "qemu-devel@nongnu.org" , Zanghongyong , Avi Kivity , "Jinxin (F)" On Thu, Nov 28, 2013 at 12:10:40PM +0100, Paolo Bonzini wrote: > Il 28/11/2013 12:09, Gleb Natapov ha scritto: > > > - if there are no callbacks, but there are readers, synchronize_srcu > > > busy-loops for some time checking if the readers complete. After a > > > while (20 us for synchronize_srcu, 120 us for > > > synchronize_srcu_expedited) it gives up and starts using a workqueue to > > > poll every millisecond. This should never happen unless > > > > Unless what ? :) Unless reader is scheduled out? > > Yes. Or unless my brain is scheduled out in the middle of a sentence. > So we will have to disable preemption in a reader to prevent big latencies for a writer, no? -- Gleb.