tcm: make pi data verification configurable
Currently ramdisk and fileio always perform PI verification
before and after backend IO. This approach is not very flexible.
Because some one may want to postpone this work to other layers in
IO stack. For example if we want to test blk_integrity_profile
testcase:
dee408c868
Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
This commit is contained in:

committed by
Nicholas Bellinger

parent
f11b55d135
commit
056e8924a0
@@ -664,6 +664,7 @@ struct se_dev_attrib {
|
||||
int pi_prot_format;
|
||||
enum target_prot_type pi_prot_type;
|
||||
enum target_prot_type hw_pi_prot_type;
|
||||
int pi_prot_verify;
|
||||
int enforce_pr_isids;
|
||||
int force_pr_aptpl;
|
||||
int is_nonrot;
|
||||
|
Reference in New Issue
Block a user