WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] blkfront and flush

To: Bruce Rogers <BROGERS@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] blkfront and flush
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 13 Jun 2008 08:27:37 +0100
Delivery-date: Fri, 13 Jun 2008 00:27:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <48515059.092E.0048.1@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcjNJvQ6Mo1LrjkaEd2YlgAWy6hiGQ==
Thread-topic: [Xen-devel] blkfront and flush
User-agent: Microsoft-Entourage/11.4.0.080122
It sounds reasonable to me, although I'm no Linux blkdev interface expert.

 -- Keir

On 12/6/08 23:35, "Bruce Rogers" <BROGERS@xxxxxxxxxx> wrote:

> Now that no-data barriers are supported/supportable, does it make sense to
> have blkfront call blk_queue_issue_flush_fn to register a flush method, which
> would use a no-data barrier request?
> 
> Is there any reason why this shouldn't work?
> 
> We have code which instead of using a  bio barrier, calls blkdev_issue_flush()
> in the linux guest, which returns -EOPNOTSUPP because that support has never
> been in blkfront.
> 
> - Bruce Rogers
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>