Searched refs:db_pi (Results 1 – 4 of 4) sorted by relevance
399 cseg->opcode = rte_cpu_to_be_32((qp->db_pi << 8) | MLX5_OPCODE_UMR); in mlx5_crypto_wqe_set()400 qp->db_pi += priv->umr_wqe_stride; in mlx5_crypto_wqe_set()413 cseg->opcode = rte_cpu_to_be_32((qp->db_pi << 8) | in mlx5_crypto_wqe_set()416 qp->db_pi += ds >> 2; in mlx5_crypto_wqe_set()422 cseg->opcode = rte_cpu_to_be_32((qp->db_pi << 8) | in mlx5_crypto_wqe_set()424 qp->db_pi += ds >> 2; /* Here, DS is 4 aligned for sure. */ in mlx5_crypto_wqe_set()466 qp->db_pi, &qp->qp_obj.db_rec[MLX5_SND_DBR], in mlx5_crypto_enqueue_burst()
55 uint16_t db_pi; member
166 qp_obj->db_pi = qp_obj->pi; in prep_one()173 size_t wqe_offset = (qp->db_pi & (qp_size_get(qp) - 1)) * in send_doorbell()177 uint32_t actual_pi = (priv->has_umr ? (qp->db_pi * 4 + 3) : qp->db_pi) & in send_doorbell()365 qp_obj->db_pi = MLX5_REGEX_UMR_QP_PI_IDX(qp_obj->pi, nb_ops - 1); in prep_regex_umr_wqe_set()
23 size_t pi, db_pi; member