From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tokarev Subject: Re: [PATCH] virtio-blk: fallback to draining the queue if barrier ops are not supported Date: Wed, 14 Oct 2009 19:38:45 +0400 Message-ID: <4AD5F085.8040909@msgid.tls.msk.ru> References: <4AD5B00D.102@redhat.com> <1255521788-24346-1-git-send-email-avi@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Christoph Hellwig , Matthew Tippett , Dustin Kirkland , Anthony Liguori , RW , kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from isrv.corpit.ru ([81.13.33.159]:34127 "EHLO isrv.corpit.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933384AbZJNPjY (ORCPT ); Wed, 14 Oct 2009 11:39:24 -0400 In-Reply-To: <1255521788-24346-1-git-send-email-avi@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Avi Kivity wrote: > Early implementations of virtio devices did not support barrier operations, > but did commit the data to disk. In such cases, drain the queue to emulate > barrier operations. Are there any implementation currently that actually supports barriers? As far as I remember there's no way to invoke barriers from a user-space application on linux, and this is how kvm/qemu is running on this OS. Thanks! /mjt