From: Kashyap Desai <kashyap.desai@broadcom.com>
To: linux-scsi@vger.kernel.org, martin.petersen@oracle.com
Subject: RE: [PATCH v2 0/4] io_uring iopoll in scsi layer
Date: Mon, 11 Jan 2021 17:45:29 +0530 [thread overview]
Message-ID: <af1ef280ded61be8ec5882b7a3b99ef9@mail.gmail.com> (raw)
In-Reply-To: <20201203034100.29716-1-kashyap.desai@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 3856 bytes --]
Hi Martin,
Due to some issue in RCU lock (only in debugging environments), there was
booting issue and shared host tag support of megaraid_sas driver is revert
backed in 5.10 -
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit
/?id=1a0e1943d8798cb3241fb5edb9a836af1611b60a
== Commit message ==
It turns out that it causes long boot-time latencies (to the point of
timeouts and failed boots).
The cause is the increase in request queues, and a fix for that is queued
up for 5.11, but we're reverting this commit that triggered the problem
for now.
==
Can you include this patch set for 5.11 ? I see (origin/5.11/scsi-queue)
has below change set. It looks like you have already queued up "shared
host tag feature for 5.11"
git log --oneline drivers/scsi/megaraid/
498854102c1c scsi: megaraid_sas: Update function description
977001df0368 scsi: megaraid_sas: Use generic power management
8ed9d987c6d9 scsi: megaraid_sas: Drop PCI wakeup calls from .resume
bba84aeccafb scsi: megaraid_sas: Simplify compat_ioctl handling
381d34e376e3 scsi: megaraid_sas: Check user-provided offsets
55e0500eb5c0 Merge tag 'scsi-misc' of
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
103fbf8e4020 scsi: megaraid_sas: Added support for shared host tagset for
cpuhotplug
62aa501dc9dd scsi: megaraid: Make smp_affinity_enable static
Kashyap
> -----Original Message-----
> From: Kashyap Desai [mailto:kashyap.desai@broadcom.com]
> Sent: Thursday, December 3, 2020 9:11 AM
> To: linux-scsi@vger.kernel.org
> Cc: Kashyap Desai <kashyap.desai@broadcom.com>
> Subject: [PATCH v2 0/4] io_uring iopoll in scsi layer
>
> This patch series is to support io_uring iopoll feature in scsi stack.
This patch
> set requires shared hosttag support.
>
> This patch set is created on top of for-next branch of
>
https://kernel.googlesource.com/pub/scm/linux/kernel/git/axboe/linux-block
>
> v2 ->
> - updated feedback from v1.
> - add reviewed-by & tested-by tag
> - remove flood of prints in scsi_debug driver during iopoll
> reported by Douglas Gilbert.
> - added new patch to support to get shost from hctx.
> added new helper function "scsi_init_hctx"
>
> v1 ->
> Fixed warnings in scsi_debug driver.
> Reported-by: kernel test robot <lkp@intel.com>
>
> Kashyap Desai (4):
> add io_uring with IOPOLL support in scsi layer
> megaraid_sas: iouring iopoll support
> scsi_debug : iouring iopoll support
> scsi: set shost as hctx driver_data
>
> drivers/scsi/megaraid/megaraid_sas.h | 2 +
> drivers/scsi/megaraid/megaraid_sas_base.c | 90 ++++++++++++--
> drivers/scsi/megaraid/megaraid_sas_fusion.c | 43 ++++++-
> drivers/scsi/megaraid/megaraid_sas_fusion.h | 3 +
> drivers/scsi/scsi_debug.c | 130 ++++++++++++++++++++
> drivers/scsi/scsi_lib.c | 28 ++++-
> include/scsi/scsi_cmnd.h | 1 +
> include/scsi/scsi_host.h | 11 ++
> 8 files changed, 294 insertions(+), 14 deletions(-)
>
>
> base-commit: 0eedceafd3a63fd082743c914853ef4b9247dbe6
> --
> 2.18.1
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4169 bytes --]
next prev parent reply other threads:[~2021-01-11 12:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 3:40 [PATCH v2 0/4] io_uring iopoll in scsi layer Kashyap Desai
2020-12-03 3:40 ` [PATCH v2 1/4] add io_uring with IOPOLL support " Kashyap Desai
2020-12-03 12:51 ` Hannes Reinecke
2020-12-04 8:53 ` John Garry
2020-12-03 3:40 ` [PATCH v2 2/4] megaraid_sas: iouring iopoll support Kashyap Desai
2020-12-03 12:57 ` Hannes Reinecke
2021-02-01 13:55 ` Kashyap Desai
2020-12-03 13:23 ` kernel test robot
2020-12-03 3:40 ` [PATCH v2 3/4] scsi_debug : " Kashyap Desai
2020-12-03 12:58 ` Hannes Reinecke
2020-12-03 19:09 ` Douglas Gilbert
2020-12-03 3:41 ` [PATCH v2 4/4] scsi: set shost as hctx driver_data Kashyap Desai
2020-12-03 13:26 ` John Garry
2020-12-03 13:30 ` Kashyap Desai
2020-12-04 9:00 ` John Garry
2021-01-11 12:15 ` Kashyap Desai [this message]
2021-01-13 3:55 ` [PATCH v2 0/4] io_uring iopoll in scsi layer 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=af1ef280ded61be8ec5882b7a3b99ef9@mail.gmail.com \
--to=kashyap.desai@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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