From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Avri Altman <avri.altman@wdc.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Bart Van Assche <bvanassche@acm.org>,
Bean Huo <beanhuo@micron.com>
Subject: Re: [PATCH v5 0/4] Untie the host lock entanglement - part 2
Date: Wed, 04 Dec 2024 13:13:58 -0500 [thread overview]
Message-ID: <yq1ldwvqpt0.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20241124070808.194860-1-avri.altman@wdc.com> (Avri Altman's message of "Sun, 24 Nov 2024 09:08:04 +0200")
Avri,
> Here is the 2nd part in the sequel, watering down the scsi host lock
> usage in the ufs driver. This work is motivated by a comment made by
> Bart [1], of the abuse of the scsi host lock in the ufs driver. Its
> Precursor [2] removed the host lock around some of the host register
> accesses.
>
> This part replaces the scsi host lock by dedicated locks serializing
> access to the clock gating and clock scaling members.
Applied to 6.14/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2024-12-04 18:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-24 7:08 [PATCH v5 0/4] Untie the host lock entanglement - part 2 Avri Altman
2024-11-24 7:08 ` [PATCH v5 1/4] scsi: ufs: core: Introduce ufshcd_has_pending_tasks Avri Altman
2024-11-25 21:28 ` Bart Van Assche
2024-11-24 7:08 ` [PATCH v5 2/4] scsi: ufs: core: Prepare to introduce a new clock_gating lock Avri Altman
2024-11-25 21:30 ` Bart Van Assche
2024-11-24 7:08 ` [PATCH v5 3/4] scsi: ufs: core: Introduce " Avri Altman
2024-11-25 21:35 ` Bart Van Assche
2025-01-21 12:42 ` Manivannan Sadhasivam
2025-01-21 12:46 ` Manivannan Sadhasivam
2025-01-21 13:24 ` Avri Altman
2024-11-24 7:08 ` [PATCH v5 4/4] scsi: ufs: core: Introduce a new clock_scaling lock Avri Altman
2024-12-04 18:13 ` Martin K. Petersen [this message]
2024-12-10 2:35 ` [PATCH v5 0/4] Untie the host lock entanglement - part 2 Martin K. Petersen
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=yq1ldwvqpt0.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.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 \
/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