From: Dolev Raviv <draviv@codeaurora.org>
To: James.Bottomley@HansenPartnership.com
Cc: linux-scsi@vger.kernel.org, linux-scsi-owner@vger.kernel.org,
sthumma@codeaurora.org, linux-arm-msm@vger.kernel.org,
Dolev Raviv <draviv@codeaurora.org>
Subject: [PATCH V1 0/4] LU queue depth manament
Date: Tue, 27 May 2014 10:21:48 +0300 [thread overview]
Message-ID: <1401175312-17753-1-git-send-email-draviv@codeaurora.org> (raw)
Some UFS devices don't support a LUN queue depth same as the device queue
depth. This requires reading the unit descriptor for extracting the LU's
queue depth.
Dolev Raviv (1):
scsi: ufs: query descriptor API
Raviv Shvili (2):
scsi: ufs: device query status and size check
scsi: ufs: Logical Unit (LU) command queue depth
Sujit Reddy Thumma (1):
scsi: ufs: Fix queue depth handling for best effort cases
drivers/scsi/ufs/ufs.h | 38 +++++-
drivers/scsi/ufs/ufshcd.c | 318 ++++++++++++++++++++++++++++++++--------------
2 files changed, 261 insertions(+), 95 deletions(-)
--
1.8.5.2
--
QUALCOMM ISRAEL, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
next reply other threads:[~2014-05-27 7:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 7:21 Dolev Raviv [this message]
2014-05-27 7:21 ` [PATCH V1 1/4] scsi: ufs: query descriptor API Dolev Raviv
2014-06-04 3:31 ` Santosh Y
2014-05-27 7:21 ` [PATCH V1 2/4] scsi: ufs: device query status and size check Dolev Raviv
2014-06-04 3:31 ` Santosh Y
2014-05-27 7:21 ` [PATCH V1 3/4] scsi: ufs: Logical Unit (LU) command queue depth Dolev Raviv
2014-06-04 3:31 ` Santosh Y
2014-05-27 7:21 ` [PATCH V1 4/4] scsi: ufs: Fix queue depth handling for best effort cases Dolev Raviv
2014-06-04 3:31 ` Santosh Y
-- strict thread matches above, loose matches on Subject: below --
2014-06-05 12:44 [PATCH V1 0/4] LU queue depth manament Dolev Raviv
2014-06-25 11:03 ` Christoph Hellwig
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=1401175312-17753-1-git-send-email-draviv@codeaurora.org \
--to=draviv@codeaurora.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-scsi-owner@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sthumma@codeaurora.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;
as well as URLs for NNTP newsgroup(s).