[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] blkfront and flush


  • To: Bruce Rogers <BROGERS@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • 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
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcjNJvQ6Mo1LrjkaEd2YlgAWy6hiGQ==
  • Thread-topic: [Xen-devel] blkfront and flush

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.