diff mbox series

[v4,1/3] block: move ref_tag calculation func to the block layer

Message ID 1532533577-1600-1-git-send-email-maxg@mellanox.com (mailing list archive)
State New, archived
Headers show
Series [v4,1/3] block: move ref_tag calculation func to the block layer | expand

Commit Message

Max Gurtovoy July 25, 2018, 3:46 p.m. UTC
Currently this function is implemented in the scsi layer, but it's
actual place should be the block layer since T10-PI is a general
data integrity feature that is used in the nvme protocol as well.

Suggested-by: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>
Cc: Martin K. Petersen <martin.petersen@oracle.com>
Signed-off-by: Max Gurtovoy <maxg@mellanox.com>
---
 drivers/infiniband/ulp/iser/iser_memory.c | 2 +-
 drivers/nvme/host/core.c                  | 3 +--
 drivers/scsi/mpt3sas/mpt3sas_scsih.c      | 2 +-
 drivers/scsi/sd_dif.c                     | 4 ++--
 include/linux/t10-pi.h                    | 6 ++++++
 include/scsi/scsi_cmnd.h                  | 7 +------
 6 files changed, 12 insertions(+), 12 deletions(-)

Comments

Martin K. Petersen July 26, 2018, 1:11 a.m. UTC | #1
Max,

> Currently this function is implemented in the scsi layer, but it's
> actual place should be the block layer since T10-PI is a general
> data integrity feature that is used in the nvme protocol as well.

Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
Jens Axboe July 27, 2018, 3:21 p.m. UTC | #2
On 7/25/18 9:46 AM, Max Gurtovoy wrote:
> Currently this function is implemented in the scsi layer, but it's
> actual place should be the block layer since T10-PI is a general
> data integrity feature that is used in the nvme protocol as well.

Applied 1-3 for 4.19.
Jens Axboe July 27, 2018, 3:38 p.m. UTC | #3
On 7/27/18 9:21 AM, Jens Axboe wrote:
> On 7/25/18 9:46 AM, Max Gurtovoy wrote:
>> Currently this function is implemented in the scsi layer, but it's
>> actual place should be the block layer since T10-PI is a general
>> data integrity feature that is used in the nvme protocol as well.
> 
> Applied 1-3 for 4.19.

This:

static inline u32 t10_pi_ref_tag(struct request *rq)
{
        return blk_rq_pos(rq) >>
                (rq->q->integrity.interval_exp - 9) & 0xffffffff;
}

won't work for !CONFIG_BLK_DEV_INTEGRITY. I didn't want to make the
change, but looks like it should either return -1U as we the value
should mean nothing if BLK_DEV_INTEGRITY isn't set, or just ignore the
shift and return blk_rq_pos(rq) & 0xffffffff.

Please fixup and resend the series.
Max Gurtovoy July 28, 2018, 10:12 p.m. UTC | #4
On 7/27/2018 6:38 PM, Jens Axboe wrote:
> On 7/27/18 9:21 AM, Jens Axboe wrote:
>> On 7/25/18 9:46 AM, Max Gurtovoy wrote:
>>> Currently this function is implemented in the scsi layer, but it's
>>> actual place should be the block layer since T10-PI is a general
>>> data integrity feature that is used in the nvme protocol as well.
>>
>> Applied 1-3 for 4.19.
> 
> This:
> 
> static inline u32 t10_pi_ref_tag(struct request *rq)
> {
>          return blk_rq_pos(rq) >>
>                  (rq->q->integrity.interval_exp - 9) & 0xffffffff;
> }
> 
> won't work for !CONFIG_BLK_DEV_INTEGRITY. I didn't want to make the
> change, but looks like it should either return -1U as we the value
> should mean nothing if BLK_DEV_INTEGRITY isn't set, or just ignore the
> shift and return blk_rq_pos(rq) & 0xffffffff.
> 
> Please fixup and resend the series.
> 

will this be good enough:

diff --git a/include/linux/t10-pi.h b/include/linux/t10-pi.h
index 81ae4c4..5a427c2 100644
--- a/include/linux/t10-pi.h
+++ b/include/linux/t10-pi.h
@@ -39,8 +39,12 @@ struct t10_pi_tuple {

  static inline u32 t10_pi_ref_tag(struct request *rq)
  {
+#ifdef CONFIG_BLK_DEV_INTEGRITY
         return blk_rq_pos(rq) >>
                 (rq->q->integrity.interval_exp - 9) & 0xffffffff;
+#else
+       return -1U;
+#endif
  }

  extern const struct blk_integrity_profile t10_pi_type1_crc;
Jens Axboe July 28, 2018, 10:22 p.m. UTC | #5
On 7/28/18 4:12 PM, Max Gurtovoy wrote:
> 
> 
> On 7/27/2018 6:38 PM, Jens Axboe wrote:
>> On 7/27/18 9:21 AM, Jens Axboe wrote:
>>> On 7/25/18 9:46 AM, Max Gurtovoy wrote:
>>>> Currently this function is implemented in the scsi layer, but it's
>>>> actual place should be the block layer since T10-PI is a general
>>>> data integrity feature that is used in the nvme protocol as well.
>>>
>>> Applied 1-3 for 4.19.
>>
>> This:
>>
>> static inline u32 t10_pi_ref_tag(struct request *rq)
>> {
>>          return blk_rq_pos(rq) >>
>>                  (rq->q->integrity.interval_exp - 9) & 0xffffffff;
>> }
>>
>> won't work for !CONFIG_BLK_DEV_INTEGRITY. I didn't want to make the
>> change, but looks like it should either return -1U as we the value
>> should mean nothing if BLK_DEV_INTEGRITY isn't set, or just ignore the
>> shift and return blk_rq_pos(rq) & 0xffffffff.
>>
>> Please fixup and resend the series.
>>
> 
> will this be good enough:
> 
> diff --git a/include/linux/t10-pi.h b/include/linux/t10-pi.h
> index 81ae4c4..5a427c2 100644
> --- a/include/linux/t10-pi.h
> +++ b/include/linux/t10-pi.h
> @@ -39,8 +39,12 @@ struct t10_pi_tuple {
> 
>   static inline u32 t10_pi_ref_tag(struct request *rq)
>   {
> +#ifdef CONFIG_BLK_DEV_INTEGRITY
>          return blk_rq_pos(rq) >>
>                  (rq->q->integrity.interval_exp - 9) & 0xffffffff;
> +#else
> +       return -1U;
> +#endif
>   }

I think so, that looks fine to me.
diff mbox series

Patch

diff --git a/drivers/infiniband/ulp/iser/iser_memory.c b/drivers/infiniband/ulp/iser/iser_memory.c
index ca844a9..130bf16 100644
--- a/drivers/infiniband/ulp/iser/iser_memory.c
+++ b/drivers/infiniband/ulp/iser/iser_memory.c
@@ -311,7 +311,7 @@  void iser_unreg_mem_fastreg(struct iscsi_iser_task *iser_task,
 {
 	domain->sig_type = IB_SIG_TYPE_T10_DIF;
 	domain->sig.dif.pi_interval = scsi_prot_interval(sc);
-	domain->sig.dif.ref_tag = scsi_prot_ref_tag(sc);
+	domain->sig.dif.ref_tag = t10_pi_ref_tag(sc->request);
 	/*
 	 * At the moment we hard code those, but in the future
 	 * we will take them from sc.
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index bf65501..191177b 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -627,8 +627,7 @@  static inline blk_status_t nvme_setup_rw(struct nvme_ns *ns,
 		case NVME_NS_DPS_PI_TYPE2:
 			control |= NVME_RW_PRINFO_PRCHK_GUARD |
 					NVME_RW_PRINFO_PRCHK_REF;
-			cmnd->rw.reftag = cpu_to_le32(
-					nvme_block_nr(ns, blk_rq_pos(req)));
+			cmnd->rw.reftag = cpu_to_le32(t10_pi_ref_tag(req));
 			break;
 		}
 	}
diff --git a/drivers/scsi/mpt3sas/mpt3sas_scsih.c b/drivers/scsi/mpt3sas/mpt3sas_scsih.c
index b8d131a..dd738ae 100644
--- a/drivers/scsi/mpt3sas/mpt3sas_scsih.c
+++ b/drivers/scsi/mpt3sas/mpt3sas_scsih.c
@@ -4568,7 +4568,7 @@  static int _scsih_set_satl_pending(struct scsi_cmnd *scmd, bool pending)
 		    MPI2_SCSIIO_EEDPFLAGS_CHECK_REFTAG |
 		    MPI2_SCSIIO_EEDPFLAGS_CHECK_GUARD;
 		mpi_request->CDB.EEDP32.PrimaryReferenceTag =
-		    cpu_to_be32(scsi_prot_ref_tag(scmd));
+		    cpu_to_be32(t10_pi_ref_tag(scmd->request));
 		break;
 
 	case SCSI_PROT_DIF_TYPE3:
diff --git a/drivers/scsi/sd_dif.c b/drivers/scsi/sd_dif.c
index 9035380..d8de43d 100644
--- a/drivers/scsi/sd_dif.c
+++ b/drivers/scsi/sd_dif.c
@@ -124,7 +124,7 @@  void sd_dif_prepare(struct scsi_cmnd *scmd)
 	if (sdkp->protection_type == T10_PI_TYPE3_PROTECTION)
 		return;
 
-	phys = scsi_prot_ref_tag(scmd);
+	phys = t10_pi_ref_tag(scmd->request);
 
 	__rq_for_each_bio(bio, scmd->request) {
 		struct bio_integrity_payload *bip = bio_integrity(bio);
@@ -176,7 +176,7 @@  void sd_dif_complete(struct scsi_cmnd *scmd, unsigned int good_bytes)
 		return;
 
 	intervals = good_bytes / scsi_prot_interval(scmd);
-	phys = scsi_prot_ref_tag(scmd);
+	phys = t10_pi_ref_tag(scmd->request);
 
 	__rq_for_each_bio(bio, scmd->request) {
 		struct bio_integrity_payload *bip = bio_integrity(bio);
diff --git a/include/linux/t10-pi.h b/include/linux/t10-pi.h
index c6aa8a3..635855e 100644
--- a/include/linux/t10-pi.h
+++ b/include/linux/t10-pi.h
@@ -37,6 +37,12 @@  struct t10_pi_tuple {
 #define T10_PI_APP_ESCAPE cpu_to_be16(0xffff)
 #define T10_PI_REF_ESCAPE cpu_to_be32(0xffffffff)
 
+static inline u32 t10_pi_ref_tag(struct request *rq)
+{
+	return blk_rq_pos(rq) >>
+		(rq->q->integrity.interval_exp - 9) & 0xffffffff;
+}
+
 extern const struct blk_integrity_profile t10_pi_type1_crc;
 extern const struct blk_integrity_profile t10_pi_type1_ip;
 extern const struct blk_integrity_profile t10_pi_type3_crc;
diff --git a/include/scsi/scsi_cmnd.h b/include/scsi/scsi_cmnd.h
index aaf1e97..cae229b 100644
--- a/include/scsi/scsi_cmnd.h
+++ b/include/scsi/scsi_cmnd.h
@@ -4,6 +4,7 @@ 
 
 #include <linux/dma-mapping.h>
 #include <linux/blkdev.h>
+#include <linux/t10-pi.h>
 #include <linux/list.h>
 #include <linux/types.h>
 #include <linux/timer.h>
@@ -313,12 +314,6 @@  static inline unsigned int scsi_prot_interval(struct scsi_cmnd *scmd)
 	return scmd->device->sector_size;
 }
 
-static inline u32 scsi_prot_ref_tag(struct scsi_cmnd *scmd)
-{
-	return blk_rq_pos(scmd->request) >>
-		(ilog2(scsi_prot_interval(scmd)) - 9) & 0xffffffff;
-}
-
 static inline unsigned scsi_prot_sg_count(struct scsi_cmnd *cmd)
 {
 	return cmd->prot_sdb ? cmd->prot_sdb->table.nents : 0;