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

[Xen-devel] RE: [PATCH 0 of 1] Patch to alter BLKIF_OP_TRIM to BLKIF_OP_DISCARD (v1).

The windows frontends in current XenServer product don't have the trim code 
enabled since the backends don't really do anything useful with it yet so I 
have no objection to a name change if it really matters that much.


> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@xxxxxxxxxx]
> Sent: 31 August 2011 04:41
> To: xen-devel@xxxxxxxxxxxxxxxxxxx; Ian Jackson; Stefano Stabellini;
> Ian Campbell; lidongyang@xxxxxxxxxx; Owen Smith; Paul Durrant;
> pasik@xxxxxx; JBeulich@xxxxxxxxxx
> Cc: konrad.wilk@xxxxxxxxxx
> Subject: [PATCH 0 of 1] Patch to alter BLKIF_OP_TRIM to
> Hey guys,
> Pasi mentioned on Li's (and Owen's) patches which provide TRIM/UNMAP
> support to the Linux backend/frontend that:
>   "
>   Isn't the generic name for this functionality "discard" in Linux?
>   and "trim" being the ATA specific discard-implementation,
>   and "scsi unmap" the SAS/SCSI specific discard-implementation?
>   Just wondering..
>   "
> and it sounds right to me. The problem is of course that the
> 'feature-trim'
> is already in the interface - but I was wondering how much it is set
> in stone? Could it be feasible to modify the backend/frontend in
> Citrix product to use 'feature-discard' instead? And naturally also
> the Novell drivers.

Xen-devel mailing list



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