 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] blkfront and flush
| To: | <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] blkfront and flush |
| From: | "Bruce Rogers" <BROGERS@xxxxxxxxxx> |
| Date: | Thu, 12 Jun 2008 16:35:42 -0600 |
| Delivery-date: | Thu, 12 Jun 2008 15:36:10 -0700 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| 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 |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] [PATCH 0/2] Improve hpet accuracy, Dan Magenheimer |
|---|---|
| Next by Date: | [Xen-devel] Xen and Kernel 2.6.25, Crazy |
| Previous by Thread: | [Xen-devel] [PATCH, resend] x86: remove use of per-domain lock from page table entry handling, Jan Beulich |
| Next by Thread: | Re: [Xen-devel] blkfront and flush, Keir Fraser |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
