search for: blkif_op_flush_diskcach

# HG changeset patch # User xen-discuss@opensolaris.org # Date 1196431468 28800 # Node ID 03e3dbd8acfbdab42ae5452973c4f9d9ff61d87b # Parent 3ae7e3ab8c510e2fdc6e010b6ca3919eb3e1aedd Add BLKIF_OP_FLUSH_DISKCACHE This disk operation, implemented on Solaris only so far, asks a backend to flush the disk caches of the underlying storage if possible, and is contigent upon the ''feature-flush-cache'' xenstore flag (although currently Solaris will always attempt to flush anyway). Signed-off-by:...

Dear list, This is the V4 of the trim support for xen-blkfront/blkback, Now we move BLKIF_OP_TRIM to BLKIF_OP_DISCARD, and dropped all "trim" stuffs in the patches, and use "discard" instead. Also we updated the helpers of blkif_x86_{32|64}_request or we will meet problems using a non-native protocol. And this patch has been tested with both SSD and raw file, with SSD we will

I am proposing these two patches for 3.2. They allow the backend to process the REQ_FUA request as well. Previous to these patches it only did REQ_FLUSH. There is also a bug-fix for the logic of how barrier/flushes were handled. The patches are based on a branch which also has ''feature-discard'' patches, so they won''t apply nativly on top of 3.1-rc5. Please review and

...quest *dst, } } +static inline void blkif_get_x86_32_req_v2(struct blkif_request_header *dst, + struct blkif_x86_32_request_v2 *src) +{ + dst->operation = src->operation; + switch (src->operation) { + case BLKIF_OP_READ: + case BLKIF_OP_WRITE: + case BLKIF_OP_WRITE_BARRIER: + case BLKIF_OP_FLUSH_DISKCACHE: + dst->u.rw.nr_segments = src->u.rw.nr_segments; + dst->u.rw.handle = src->u.rw.handle; + dst->u.rw.id = src->u.rw.id; + dst->u.rw.sector_number = src->u.rw.sector_number; + dst->u.rw.seg_id = src->u.rw.seg_id; + barrier(); + break; + case BLKIF_OP_DISCARD: +...

.... In particular, contrary to the message below, the user subsequently confirmed that the issue appears to be Xen specific (doesn''t happen on native or vmware) and that it arose between 2.6.39-2-686-pae and 3.0.0-1-686-pae. Could it be related to edf6ef59ec7e "xen-blkfront: Introduce BLKIF_OP_FLUSH_DISKCACHE support"? That looks like the only pertinent change between 2.6.39 and 3.0. Gedalya, 2.6.39-2-686-pae could be anything from v2.6.39..v2.6.39.2 please could you confirm which package version you have installed in case it makes a difference. Cheers, Ian. On Tue, 2011-08-09 at 14:07 -0400, G...

...nfo->rq, info->feature_flush); - printk(KERN_INFO "blkfront: %s: %s: %s\n", + printk(KERN_INFO "blkfront: %s: %s: %s. Persistent=%d\n", info->gd->disk_name, info->flush_op == BLKIF_OP_WRITE_BARRIER ? "barrier" : (info->flush_op == BLKIF_OP_FLUSH_DISKCACHE ? "flush diskcache" : "barrier or flush"), - info->feature_flush ? "enabled" : "disabled"); + info->feature_flush ? "enabled" : "disabled", + info->feature_persistent); } static int xen_translate_vdev(int...