From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Kashyap Desai <kashyap.desai@broadcom.com>
Cc: Hannes Reinecke <hare@suse.de>,
Christoph Hellwig <hch@infradead.org>,
Sreekanth Reddy <sreekanth.reddy@broadcom.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
Sathya Prakash <Sathya.Prakash@broadcom.com>,
Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v1] mpt3sas: Use driver scsi lookup to track outstanding IOs
Date: Wed, 27 Feb 2019 09:50:08 -0500 [thread overview]
Message-ID: <yq14l8p9tgf.fsf@oracle.com> (raw)
In-Reply-To: <CAHsXFKGbNfJ32EE_Gyz9yC0k+yNB=rgMQZc+jAQr2nFPDC+oFg@mail.gmail.com> (Kashyap Desai's message of "Tue, 26 Feb 2019 21:35:10 +0530")
Kashyap,
> Primary drawback of using "blk_mq_tagset_busy_iter" is API is only for
> blk-mq and it is not available for all the kernel with blk-mq
> support. We have seen multiple failures from customer and those
> kernels does not support blk_mq_tagset_busy_iter. In fact, blk-mq and
> non-mq stack is alive in many Linux distribution and customer is using
> those.
I'm afraid the burden falls upon Broadcom to manage enablement patches
for older kernels. So the non-MQ/non-tagset-busy-iter cases are not
particularly relevant for the discussion here.
Let's focus on getting some usable plumbing that drivers can use to
abort oustanding tags.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-02-27 14:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 12:11 [PATCH v1] mpt3sas: Use driver scsi lookup to track outstanding IOs Sreekanth Reddy
2019-02-21 12:11 ` Sreekanth Reddy
[not found] ` <20190222152433.CF1822086A@mail.kernel.org>
2019-02-25 5:12 ` Sreekanth Reddy
2019-02-25 19:08 ` Hannes Reinecke
2019-02-26 11:48 ` Sreekanth Reddy
2019-02-26 12:28 ` Hannes Reinecke
2019-02-26 13:12 ` Sreekanth Reddy
2019-02-26 13:49 ` Hannes Reinecke
2019-02-26 13:49 ` Hannes Reinecke
2019-02-26 14:33 ` Christoph Hellwig
2019-02-26 14:40 ` Martin K. Petersen
2019-02-26 14:53 ` Hannes Reinecke
2019-02-26 16:05 ` Kashyap Desai
2019-02-27 14:50 ` Martin K. Petersen [this message]
2019-02-28 13:25 ` Sreekanth Reddy
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=yq14l8p9tgf.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Sathya.Prakash@broadcom.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=kashyap.desai@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sreekanth.reddy@broadcom.com \
--cc=stable@vger.kernel.org \
--cc=suganath-prabu.subramani@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.