On Mon, Jan 30 2012 at 7:31pm -0500, Martin K. Petersen <martin.petersen@xxxxxxxxxx> wrote: > diff --git a/Documentation/ABI/testing/sysfs-block b/Documentation/ABI/testing/sysfs-block > index c1eb41c..e5f4194 100644 > --- a/Documentation/ABI/testing/sysfs-block > +++ b/Documentation/ABI/testing/sysfs-block > @@ -206,3 +206,16 @@ Description: > when a discarded area is read the discard_zeroes_data > parameter will be set to one. Otherwise it will be 0 and > the result of reading a discarded area is undefined. > + > +What: /sys/block/<disk>/queue/max_write_same_bytes > +Date: January 2012 > +Contact: Martin K. Petersen <martin.petersen@xxxxxxxxxx> > +Description: > + Some devices support a write same operation in which a > + single data block can be written to a range of several > + contiguous blocks on storage. This can be used to wipe > + areas on disk or to initialize drives in a RAID > + configuration. max_write_same_bytes indicates how many > + bytes can be written in a single write same command. If > + max_write_same_bytes is 0, write same is not supported > + by the device. How about write_same_max_bytes to follow the pattern established with /sys/block/<disk>/queue/discard_max_bytes? -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
