From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [Qemu-devel] [PATCH] ceph/rbd block driver for qemu-kvm (v4) Date: Thu, 07 Oct 2010 16:04:05 -0500 Message-ID: <4CAE35C5.2010809@codemonkey.ws> References: <20100802194631.GA4923@chb-desktop> <20100803201407.GD1475@chb-desktop> <4CADD567.9010606@codemonkey.ws> <4CAE13BA.70707@codemonkey.ws> <4CAE24C5.8030007@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Kevin Wolf , kvm@vger.kernel.org, qemu-devel@nongnu.org, ceph-devel@vger.kernel.org, Christian Brunner To: Yehuda Sadeh Weinraub Return-path: In-Reply-To: Sender: ceph-devel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 10/07/2010 03:47 PM, Yehuda Sadeh Weinraub wrote: >> How is that possible? Are the callbacks delivered in the context of a >> different thread? If so, don't you need locking? >> > Not sure I'm completely following you. The callbacks are delivered in > the context of a different thread, but won't run concurrently. Concurrently to what? How do you prevent them from running concurrently with qemu? If you saw lock ups, I bet that's what it was from. Regards, Anthony Liguori > Do you > see any specific concurrency issue? We can add some mutex protection > around at the aio callback, so that if librados turns multithreaded at > this point we're covered. > > > Thanks, > Yehuda > >