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

[Xen-devel] Block WRITE_BARRIER / FLUSH_DISKCACHE operations and paramet

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Block WRITE_BARRIER / FLUSH_DISKCACHE operations and parameters
From: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>
Date: Thu, 7 Feb 2008 16:14:42 +0000
Delivery-date: Thu, 07 Feb 2008 08:15:59 -0800
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>
Mail-followup-to: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.12-2006-07-14
Hello,

Nothing is said about parameters to be given along WRITE_BARRIER or
FLUSH_DISKCACHE operations.  I guess they are both implicitely supposed
to be write operations? (it's the case for WRITE_BARRIER in the Linux
implementation) If so, would it be fine to allow nr_segments to be 0?
As part of IDE cache flush emulation, I need to issue WRITE_BARRIERs
without issuing any actual write...

Samuel

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

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