[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 1 of 1] interface: BLKIF_OP_TRIM -> BLKIF_OP_DISCARD
On Wed, Oct 12, 2011 at 11:40:04AM +0100, Ian Campbell wrote: > On Tue, 2011-10-11 at 19:27 +0100, Konrad Rzeszutek Wilk wrote: > > On Mon, Oct 10, 2011 at 03:58:42PM -0400, Konrad Rzeszutek Wilk wrote: > > > On Mon, Oct 10, 2011 at 01:50:11PM -0400, Konrad Rzeszutek Wilk wrote: > > > > Per Ian and Jan's suggestion (note, the structure is 4-byte aligned > > so we do not need to pad it): > > > > # HG changeset patch > > # Parent 72f339bc600d7a9629d3f9eb8a279fbf8be25b12 > > interface: BLKIF_OP_TRIM -> BLKIF_OP_DISCARD > > > > The name 'trim' is specific to the ATA discard implementation. > > The name 'scsi unmap' is specific to the SCSI discard implementation. > > > > We should really use a generic name - and the name 'discard' > > looks to be the most generic of them all. Also update the description > > to mention the other parameters that the frontend can query the > > backend for: discard-aligment, discard-granularity, and > > discard-secure. We also utilize per Jan Beulich keen suggestion, > > the 8-bit reserved field to use as a flag value. Currently the only > > flag that can be passed for a discard operation is secure delete: > > BLKIF_OP_DISCARD_FLAG_SECURE. > > This change seems to be conflating a large rename with new data fields, > changes to the documentation in the comments and other bits and bobs, > which makes it pretty hard to review it's actual impact. Can we get them > separately? Of course. Sent them along with Jan's Acked-by flag. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |