public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter Wang (王信友)" <peter.wang@mediatek.com>
To: "beanhuo@micron.com" <beanhuo@micron.com>,
	"sh043.lee@samsung.com" <sh043.lee@samsung.com>,
	"avri.altman@wdc.com" <avri.altman@wdc.com>,
	"storage.sec@samsung.com" <storage.sec@samsung.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"bvanassche@acm.org" <bvanassche@acm.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
	"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Subject: Re: [PATCH] UFS: Make TM command timeout configurable from host side
Date: Mon, 17 Nov 2025 08:40:46 +0000	[thread overview]
Message-ID: <500022ecc5216afa01e7f606187f012294a76da3.camel@mediatek.com> (raw)
In-Reply-To: <000001dc5791$5f2ea880$1d8bf980$@samsung.com>

On Mon, 2025-11-17 at 16:11 +0900, Seunghui Lee wrote:
> Hi Mr.Wang,
> 
> I understand your concerns about considering the worst-case scenario.
> What about directly modifying TM_CMD_TIMEOUT (100ms -> 300ms) and
> reducing the TM retry count from 100 to 30?
> 
> Please let me know your opinion.
> 


Hi Seunghui,

Changing TM_CMD_TIMEOUT from 100ms to 300ms is okay for me.
The adjustment of the TM retry count from 100 to 30 is not 
significant, so it does not matter whether this change is 
made or not. Overall, this patch looks good to me.

However, the other TM clear timeout of 1 second has a much
greater impact:
ufshcd_wait_for_register(hba, REG_UTP_TRANSFER_REQ_DOOR_BELL, 
    mask, ~mask, 1000, 1000);
Would you consider shortening this value as well?

Thanks
Peter



> Thank you,
> Seunghui Lee.
> 
> --- a/drivers/ufs/core/ufshcd.c
> +++ b/drivers/ufs/core/ufshcd.c
> @@ -68,7 +68,7 @@ enum {
>  #define ADVANCED_RPMB_REQ_TIMEOUT  3000 /* 3 seconds */
> 
>  /* Task management command timeout */
> -#define TM_CMD_TIMEOUT 100 /* msecs */
> +#define TM_CMD_TIMEOUT 300 /* msecs */
> 
>  /* maximum number of retries for a general UIC command  */
>  #define UFS_UIC_COMMAND_RETRIES 3
> @@ -7663,7 +7663,7 @@ int ufshcd_try_to_abort_task(struct ufs_hba
> *hba, int tag)
>         int poll_cnt;
>         u8 resp = 0xF;
> 
> -       for (poll_cnt = 100; poll_cnt; poll_cnt--) {
> +       for (poll_cnt = 30; poll_cnt; poll_cnt--) {
>                 err = ufshcd_issue_tm_cmd(hba, lrbp->lun, lrbp-
> >task_tag,
>                                 UFS_QUERY_TASK, &resp);
>                 if (!err && resp ==
> UPIU_TASK_MANAGEMENT_FUNC_SUCCEEDED) {
> 
> 
> 


  reply	other threads:[~2025-11-17  8:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20251106012702epcas1p28fdeed020ea44f18dcc751c283fbbcc2@epcas1p2.samsung.com>
2025-11-06  1:26 ` [PATCH] UFS: Make TM command timeout configurable from host side Seunghui Lee
2025-11-11  2:46   ` Peter Wang (王信友)
2025-11-11  8:44     ` Seunghui Lee
2025-11-11  9:03       ` Peter Wang (王信友)
2025-11-11 16:37         ` Bart Van Assche
2025-11-12  2:58           ` Peter Wang (王信友)
2025-11-12  8:49             ` Seunghui Lee
2025-11-12  9:42               ` Peter Wang (王信友)
2025-11-12 16:51             ` Bart Van Assche
2025-11-13 10:08               ` Peter Wang (王信友)
2025-11-17  7:11                 ` Seunghui Lee
2025-11-17  8:40                   ` Peter Wang (王信友) [this message]
2025-11-17  9:48                     ` Seunghui Lee
2025-11-18  5:48                       ` Peter Wang (王信友)
2025-11-17 16:43                   ` Bart Van Assche
2025-11-18  5:55                     ` Peter Wang (王信友)
2025-11-18 17:31                       ` Bart Van Assche
2025-11-19  9:20                         ` Peter Wang (王信友)
2025-11-17 16:40                 ` Bart Van Assche
2025-11-18  5:52                   ` Peter Wang (王信友)
2025-11-11 16:38   ` Bart Van Assche

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=500022ecc5216afa01e7f606187f012294a76da3.camel@mediatek.com \
    --to=peter.wang@mediatek.com \
    --cc=adrian.hunter@intel.com \
    --cc=alim.akhtar@samsung.com \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=sh043.lee@samsung.com \
    --cc=storage.sec@samsung.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox