From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=42148 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OEfcK-00029V-N7 for qemu-devel@nongnu.org; Wed, 19 May 2010 05:31:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OEfcG-0004Ej-MZ for qemu-devel@nongnu.org; Wed, 19 May 2010 05:31:08 -0400 Received: from verein.lst.de ([213.95.11.210]:45418) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OEfcG-0004EU-E9 for qemu-devel@nongnu.org; Wed, 19 May 2010 05:31:04 -0400 Date: Wed, 19 May 2010 11:31:01 +0200 From: Christoph Hellwig Message-ID: <20100519093101.GA6403@lst.de> References: <1274203124-14318-1-git-send-email-avi@redhat.com> <4BF39CA3.9020305@redhat.com> <4BF3AA1E.4050307@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: [Qemu-devel] Re: [PATCH +stable] block: don't attempt to merge overlapping requests List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Kevin Wolf , Christoph Hellwig , Avi Kivity , kvm@vger.kernel.org, qemu-devel@nongnu.org On Wed, May 19, 2010 at 10:23:44AM +0100, Stefan Hajnoczi wrote: > On Wed, May 19, 2010 at 10:06 AM, Avi Kivity wrote: > >> In the cache=writeback case the virtio-blk guest driver does: > >> > >> blk_queue_ordered(q, QUEUE_ORDERED_DRAIN_FLUSH, ...) > >> > > > > I don't follow. ?What's the implication? > > I was wondering whether the queue is incorrectly set to a mode where > overlapping write requests aren't being ordered. Anyway, Christoph > says overlapping write requests can be issued so my theory is broken. They can happen, but won't during usual pagecache based writeback. So this should not happen for the pagecache based mke2fs workload. It could happen for a workload with mkfs that uses O_DIRECT. And we need to handle it either way. And btw, our barrier handling for devices using multiwrite (aka virtio) is utterly busted right now, patch will follow ASAP.