diff options
| author |   Max Gurtovoy <maxg@mellanox.com> | 2019-09-16 18:44:29 +0300 |
|---|---|---|
| committer |   Jens Axboe <axboe@kernel.dk> | 2019-09-17 20:03:49 -0600 |
| commit | 54d4e6ab91eb24b47a58403d8561206e916f0242 (patch) | |
| tree | 3bd64c92b614284071d893012abcf01bfc55cabc /block/blk.h | |
| parent | block: use symbolic constants for t10_pi type (diff) | |
| download | linux-dev-54d4e6ab91eb24b47a58403d8561206e916f0242.tar.xz linux-dev-54d4e6ab91eb24b47a58403d8561206e916f0242.zip | |
block: centralize PI remapping logic to the block layer
Currently t10_pi_prepare/t10_pi_complete functions are called during the
NVMe and SCSi layers command preparetion/completion, but their actual
place should be the block layer since T10-PI is a general data integrity
feature that is used by block storage protocols. Introduce .prepare_fn
and .complete_fn callbacks within the integrity profile that each type
can implement according to its needs.
Suggested-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Suggested-by: Martin K. Petersen <martin.petersen@oracle.com>
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
Signed-off-by: Max Gurtovoy <maxg@mellanox.com>
Fixed to not call queue integrity functions if BLK_DEV_INTEGRITY
isn't defined in the config.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/blk.h')
0 files changed, 0 insertions, 0 deletions