From: Bart Van Assche <bvanassche@acm.org>
To: daejun7.park@samsung.com, ALIM AKHTAR <alim.akhtar@samsung.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"asutoshd@codeaurora.org" <asutoshd@codeaurora.org>,
"beanhuo@micron.com" <beanhuo@micron.com>,
"stanley.chu@mediatek.com" <stanley.chu@mediatek.com>,
"cang@codeaurora.org" <cang@codeaurora.org>,
"tomas.winkler@intel.com" <tomas.winkler@intel.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sang-yoon Oh <sangyoon.oh@samsung.com>,
Sung-Jun Park <sungjun07.park@samsung.com>,
yongmyung lee <ymhungry.lee@samsung.com>,
Jinyoung CHOI <j-young.choi@samsung.com>,
Adel Choi <adel.choi@samsung.com>,
BoRam Shin <boram.shin@samsung.com>
Subject: Re: [RFC PATCH 2/5] scsi: ufs: Add UFS-feature layer
Date: Thu, 11 Jun 2020 21:28:34 -0700 [thread overview]
Message-ID: <cf01e1d2-50e9-7fa8-b2ee-88a900231304@acm.org> (raw)
In-Reply-To: <20200612022759epcms2p47929b76eb2e809240f415c19f9383f92@epcms2p4>
On 2020-06-11 19:27, Daejun Park wrote:
>>> @@ -2525,6 +2525,8 @@ static int ufshcd_queuecommand(struct Scsi_Host *host, struct scsi_cmnd *cmd)
>>>
>>> ufshcd_comp_scsi_upiu(hba, lrbp);
>>>
>>> + ufsf_ops_prep_fn(hba, lrbp);
>>> +
>>> err = ufshcd_map_sg(hba, lrbp);
>>> if (err) {
>>> lrbp->cmd = NULL;
>
>> What happens if a SCSI command is retried and hence ufsf_ops_prep_fn()
>> is called multiple times for the same SCSI command?
>
> Developers of UFS features should implement it so that prep_fn does not have
> any problems even if it processes the same SCSI command multiple times.
> In HPB feature, prep_fn modifies only upiu structure. So it is ok to call
> it multiple times because the upiu is rebuilt from ufshcd_comp_scsi_upiu().
Please make sure that this expectation is documented somewhere.
Thanks,
Bart.
next prev parent reply other threads:[~2020-06-12 4:28 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200605011604epcms2p8bec8ef6682583d7248dc7d9dc1bfc882@epcms2p8>
2020-06-05 1:16 ` [RFC PATCH 0/5] scsi: ufs: Add Host Performance Booster Support Daejun Park
2020-06-05 1:22 ` [RFC PATCH 1/5] scsi: ufs: Add UFS feature related parameter Daejun Park
2020-06-05 1:30 ` [RFC PATCH 2/5] scsi: ufs: Add UFS-feature layer Daejun Park
2020-06-05 1:38 ` [RFC PATCH 3/5] scsi: ufs: Introduce HPB module Daejun Park
2020-06-05 1:56 ` [RFC PATCH 4/5] scsi: ufs: L2P map management for HPB read Daejun Park
2020-06-05 2:12 ` [RFC PATCH 5/5] scsi: ufs: Prepare HPB read for cached sub-region Daejun Park
2020-06-06 18:38 ` Avri Altman
2020-06-09 0:53 ` Daejun Park
2020-06-09 1:23 ` Bart Van Assche
2020-06-11 1:37 ` Bart Van Assche
2020-06-11 6:43 ` Avri Altman
2020-06-12 3:39 ` Daejun Park
2020-06-06 18:26 ` [RFC PATCH 4/5] scsi: ufs: L2P map management for HPB read Avri Altman
2020-06-09 0:52 ` Daejun Park
2020-06-09 6:39 ` Avri Altman
2020-06-10 2:49 ` Daejun Park
2020-06-09 6:48 ` Avri Altman
2020-06-10 3:51 ` Daejun Park
2020-06-09 1:15 ` Bart Van Assche
2020-06-11 1:16 ` Bart Van Assche
2020-06-12 3:37 ` Daejun Park
2020-06-13 15:24 ` Bart Van Assche
2020-06-06 14:58 ` [RFC PATCH 3/5] scsi: ufs: Introduce HPB module Avri Altman
2020-06-09 0:52 ` Daejun Park
2020-06-09 6:51 ` Avri Altman
2020-06-12 2:25 ` Daejun Park
2020-06-07 7:06 ` Avri Altman
2020-06-09 0:53 ` Daejun Park
2020-06-10 4:29 ` Bart Van Assche
2020-06-10 9:57 ` Bean Huo
2020-06-12 2:29 ` Daejun Park
2020-06-10 4:15 ` [RFC PATCH 2/5] scsi: ufs: Add UFS-feature layer Bart Van Assche
2020-06-12 2:27 ` Daejun Park
2020-06-12 4:28 ` Bart Van Assche [this message]
2020-06-11 1:39 ` Bart Van Assche
2020-06-06 12:11 ` [RFC PATCH 1/5] scsi: ufs: Add UFS feature related parameter Avri Altman
2020-06-09 0:51 ` Daejun Park
2020-06-06 12:02 ` [RFC PATCH 0/5] scsi: ufs: Add Host Performance Booster Support Avri Altman
2020-06-09 0:49 ` Daejun Park
2020-06-09 7:00 ` Avri Altman
2020-06-10 9:50 ` Bean Huo
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=cf01e1d2-50e9-7fa8-b2ee-88a900231304@acm.org \
--to=bvanassche@acm.org \
--cc=adel.choi@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=boram.shin@samsung.com \
--cc=cang@codeaurora.org \
--cc=daejun7.park@samsung.com \
--cc=j-young.choi@samsung.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sangyoon.oh@samsung.com \
--cc=stanley.chu@mediatek.com \
--cc=sungjun07.park@samsung.com \
--cc=tomas.winkler@intel.com \
--cc=ymhungry.lee@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