All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryant G. Ly" <bryantly@linux.vnet.ibm.com>
To: lixiubo@cmss.chinamobile.com, agrover@redhat.com,
	nab@linux-iscsi.org, mchristi@redhat.com
Cc: shli@kernel.org, sheng@yasker.org, linux-scsi@vger.kernel.org,
	target-devel@vger.kernel.org, namei.unix@gmail.com
Subject: Re: [PATCHv2 5/5] target/user: Clean up tcmu_queue_cmd_ring
Date: Thu, 16 Mar 2017 15:50:03 -0500	[thread overview]
Message-ID: <7d9016c5-e067-bb35-756f-8a7fd143e6af@linux.vnet.ibm.com> (raw)
In-Reply-To: <1488962743-17028-6-git-send-email-lixiubo@cmss.chinamobile.com>


> From: Xiubo Li <lixiubo@cmss.chinamobile.com>
>
> Add two helpers to simplify the code, and move some code out of
> the cmdr spin lock to reduce the size of critical region.
>
> Signed-off-by: Xiubo Li <lixiubo@cmss.chinamobile.com>
> ---
>   drivers/target/target_core_user.c | 54 ++++++++++++++++++++++-----------------
>   1 file changed, 30 insertions(+), 24 deletions(-)
>
> diff --git a/drivers/target/target_core_user.c b/drivers/target/target_core_user.c
> index 117be07..5205d2f 100644
> --- a/drivers/target/target_core_user.c
> +++ b/drivers/target/target_core_user.c

<SNIP>

>
> +static inline void tcmu_cmd_get_cmd_size(struct se_cmd *se_cmd,
> +			size_t *base_size, size_t *cmd_size)

Should this be tcmu_cmd_get_cmd_size(struct tcmu_cmd *tcmu_cmd instead? Look at bottom.

> +{
> +	struct se_cmd *se_cmd = tcmu_cmd->se_cmd;
> +
> +	*base_size = max(offsetof(struct tcmu_cmd_entry,
> +				 req.iov[tcmu_cmd->dbi_len]),
> +				 sizeof(struct tcmu_cmd_entry));
> +
> +	*cmd_size = round_up(scsi_command_size(se_cmd->t_task_cdb),
> +			TCMU_OP_ALIGN_SIZE) + *base_size;
> +	WARN_ON(*cmd_size & (TCMU_OP_ALIGN_SIZE-1));
> +}
> +
>   static sense_reason_t
>   tcmu_queue_cmd_ring(struct tcmu_cmd *tcmu_cmd)
>   {
>   	struct tcmu_dev *udev = tcmu_cmd->tcmu_dev;
>   	struct se_cmd *se_cmd = tcmu_cmd->se_cmd;
>   	size_t base_command_size, command_size;
> -	struct tcmu_mailbox *mb;
> +	struct tcmu_mailbox *mb = udev->mb_addr;
>   	struct tcmu_cmd_entry *entry;
>   	struct iovec *iov;
>   	int iov_cnt, ret;
> @@ -642,6 +660,8 @@ static bool is_ring_space_avail(struct tcmu_dev *udev, struct tcmu_cmd *cmd,
>   	if (test_bit(TCMU_DEV_BIT_BROKEN, &udev->flags))
>   		return TCM_LOGICAL_UNIT_COMMUNICATION_FAILURE;
>
> +	if (se_cmd->se_cmd_flags & SCF_BIDI)
> +		BUG_ON(!(se_cmd->t_bidi_data_sg && se_cmd->t_bidi_data_nents));
>   	/*
>   	 * Must be a certain minimum size for response sense info, but
>   	 * also may be larger if the iov array is large.
> @@ -649,33 +669,19 @@ static bool is_ring_space_avail(struct tcmu_dev *udev, struct tcmu_cmd *cmd,
>   	 * We prepare way too many iovs for potential uses here, because it's
>   	 * expensive to tell how many regions are freed in the bitmap
>   	*/
> -	base_command_size = max(offsetof(struct tcmu_cmd_entry,
> -				req.iov[tcmu_cmd->dbi_len]),
> -				sizeof(struct tcmu_cmd_entry));
> -	command_size = base_command_size
> -		+ round_up(scsi_command_size(se_cmd->t_task_cdb), TCMU_OP_ALIGN_SIZE);
> -
> -	WARN_ON(command_size & (TCMU_OP_ALIGN_SIZE-1));
> -
> -	spin_lock_irq(&udev->cmdr_lock);
> -
> -	mb = udev->mb_addr;
> -	cmd_head = mb->cmd_head % udev->cmdr_size; /* UAM */
> -	data_length = round_up(se_cmd->data_length, DATA_BLOCK_SIZE);
> -	if (se_cmd->se_cmd_flags & SCF_BIDI) {
> -		BUG_ON(!(se_cmd->t_bidi_data_sg && se_cmd->t_bidi_data_nents));
> -		data_length += round_up(se_cmd->t_bidi_data_sg->length,
> -				DATA_BLOCK_SIZE);
> -	}
> +	tcmu_cmd_get_cmd_size(tcmu_cmd, &base_command_size, &command_size);

<SNIP>

So Based upon your definition of tcmu_cmd_get_cmd_size, why did you pass in tcmu_cmd here? It wont compile in its current state.

-Bryant

      reply	other threads:[~2017-03-16 23:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08  8:45 [PATCHv2 0/5] Dynamic growing data area support lixiubo
2017-03-08  8:45 ` [PATCHv2 1/5] target/user: Add dynamic growing data area feature support lixiubo
2017-03-08  8:45 ` [PATCHv2 2/5] target/user: Add global data block pool support lixiubo
2017-03-08 20:20   ` Andy Grover
2017-03-16  9:39     ` Xiubo Li
2017-03-17  8:04       ` Xiubo Li
2017-03-17  8:04         ` Xiubo Li
2017-03-17 17:11         ` Andy Grover
2017-03-17 22:06           ` 李秀波
2017-03-08  8:45 ` [PATCHv2 3/5] target/user: Fix possible overwrite of t_data_sg's last iov[] lixiubo
2017-03-16 18:23   ` Bryant G. Ly
2017-03-08  8:45 ` [PATCHv2 4/5] target/user: Fix wrongly calculating of the base_command_size lixiubo
2017-03-17  5:45   ` Xiubo Li
2017-03-08  8:45 ` [PATCHv2 5/5] target/user: Clean up tcmu_queue_cmd_ring lixiubo
2017-03-16 20:50   ` Bryant G. Ly [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7d9016c5-e067-bb35-756f-8a7fd143e6af@linux.vnet.ibm.com \
    --to=bryantly@linux.vnet.ibm.com \
    --cc=agrover@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lixiubo@cmss.chinamobile.com \
    --cc=mchristi@redhat.com \
    --cc=nab@linux-iscsi.org \
    --cc=namei.unix@gmail.com \
    --cc=sheng@yasker.org \
    --cc=shli@kernel.org \
    --cc=target-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.