> Subject: Re: SQ overflow seen running isert traffic with high block sizes
>
>
> First, would it be helpful to limit maximum payload size per I/O for consumers
> based on number of iser-target sq hw sges..?
>
Assuming data is not able to be fast registered as if virtually contiguous;
artificially limiting the data size might not be the best solution.
But max SGEs does need to be exposed higher. Somewhere in the stack,
there might need to be multiple WRs submitted or data copied.
> diff --git a/drivers/target/iscsi/iscsi_target_configfs.c
> b/drivers/target/iscsi/iscsi_target_configf
> index 0ebc481..d8a4cc5 100644
> --- a/drivers/target/iscsi/iscsi_target_configfs.c
> +++ b/drivers/target/iscsi/iscsi_target_configfs.c
> @@ -1553,6 +1553,7 @@ static void lio_release_cmd(struct se_cmd *se_cmd)
> .module = THIS_MODULE,
> .name = "iscsi",
> .node_acl_size = sizeof(struct iscsi_node_acl),
> + .max_data_sg_nents = 32, /* 32 * PAGE_SIZE = MAXIMUM
> TRANSFER LENGTH */
> .get_fabric_name = iscsi_get_fabric_name,
> .tpg_get_wwn = lio_tpg_get_endpoint_wwn,
> .tpg_get_tag = lio_tpg_get_tag,
>
BTW, this is helping the SQ overflow issue.
��.n��������+%������w��{.n�����{���fk��ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
