History

block: Deprecate the use of the term sector in the context of block integrity

The protection interval is not necessarily tied to the logical block size of a block device. Stop using the terms "sector" and "sectors". Going forward we will use the term "seed" to describe the initial reference tag value for a given I/O. "Interval" will be used to describe the portion of the data buffer that a given piece of protection information is associated with.

Martin K. Petersen committed 12 years ago

Commit 3be91c41 parent 5f9378f4 files · +52 −52Browse files

Showing the changes to include/linux/blkdev.h (1 of 4 files). Show all

Unified · Split

include/linux/blkdev.h+3−3
@@ -1464,9 +1464,9 @@ static inline uint64_t rq_io_start_time_ns(struct request *req) · 1463 unmodified lines
14641464 struct blk_integrity_exchg {
14651465 void *prot_buf;
14661466 void *data_buf;
1467− sector_t sector;
1467+ sector_t seed;
14681468 unsigned int data_size;
1469− unsigned short sector_size;
1469+ unsigned short interval;
14701470 const char *disk_name;
14711471 };
14721472
@@ -1479,7 +1479,7 @@ struct blk_integrity { · 6 unmodified lines
14791479
14801480 unsigned short flags;
14811481 unsigned short tuple_size;
1482− unsigned short sector_size;
1482+ unsigned short interval;
14831483 unsigned short tag_size;
14841484
14851485 const char *name;