From: Niklas Cassel <cassel@kernel.org>
To: yangxingui <yangxingui@huawei.com>
Cc: John Garry <john.g.garry@oracle.com>,
Yihang Li <liyihang9@huawei.com>,
martin.petersen@oracle.com,
James.Bottomley@hansenpartnership.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxarm@huawei.com, liuyonglong@huawei.com,
prime.zeng@hisilicon.com, dlemoal@kernel.org
Subject: Re: [PATCH 1/5] scsi: hisi_sas: Add host_tagset_enable module param for v3 hw
Date: Mon, 31 Mar 2025 10:40:59 +0200 [thread overview]
Message-ID: <Z-pVGyZ1vMBhUfYH@ryzen> (raw)
In-Reply-To: <e5ab4e5a-33d0-6102-1c5c-f1f83a752346@huawei.com>
Hello Xingui,
On Sat, Mar 29, 2025 at 05:49:47PM +0800, yangxingui wrote:
> Hi,John
>
> On 2025/3/29 16:50, John Garry wrote:
> > On 29/03/2025 07:32, Yihang Li wrote:
> >
> > +
> >
> > > From: Xingui Yang<yangxingui@huawei.com>
> > >
> > > After driver exposes all HW queues and application submits IO to multiple
> > > queues in parallel, if NCQ and non-NCQ commands are mixed to sata disk,
> > > ata_qc_defer() causes non-NCQ commands to be requeued and possibly
> > > repeated
> > > forever.
> >
> > I don't think that it is a good idea to mask out bugs with module
> > parameters.
> >
> > Was this the same libata/libsas issue reported some time ago?
>
> Yeah,related to this issue: https://lore.kernel.org/linux-block/eef1e927-c9b2-c61d-7f48-92e65d8b0418@huawei.com/
>
> And, Niklas tried to help fix this problem:
> https://lore.kernel.org/linux-scsi/ZynmfyDA9R-lrW71@ryzen/
>
> Considering that there is no formal solution yet. And our users rarely use
> SATA disks and SAS disks together on a single machine. For this reason, they
> can flexibly turn off the exposure of multiple queues in the scenario of
> using only SATA disks. In addition, it is also convenient to conduct
> performance comparison tests to expose multiple hardware queues and single
> queues.
The solution I sent is not good since it relies on EH.
One would need to come up with a better solution to fix libsas drivers,
possibly a workqueue.
I think Damien is planning to add a workqueue submit path to libata,
if so, perhaps we could base a better solution on top of that.
Kind regards,
Niklas
next prev parent reply other threads:[~2025-03-31 8:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-29 7:32 [PATCH 0/5] hisi_sas: Misc patches and cleanups Yihang Li
2025-03-29 7:32 ` [PATCH 1/5] scsi: hisi_sas: Add host_tagset_enable module param for v3 hw Yihang Li
2025-03-29 8:50 ` John Garry
2025-03-29 9:49 ` yangxingui
2025-03-31 7:43 ` John Garry
2025-04-01 1:12 ` yangxingui
2025-03-31 8:40 ` Niklas Cassel [this message]
2025-03-31 10:29 ` Yihang Li
2025-04-01 1:18 ` yangxingui
2025-03-29 7:32 ` [PATCH 2/5] scsi: hisi_sas: Use macro instead of magic number Yihang Li
2025-03-29 7:32 ` [PATCH 3/5] scsi: hisi_sas: Code style cleanup Yihang Li
2025-03-29 7:32 ` [PATCH 4/5] scsi: hisi_sas: Call I_T_nexus after soft reset for SATA disk Yihang Li
2025-03-29 7:32 ` [PATCH 5/5] scsi: hisi_sas: Wait until eh is recovered Yihang Li
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=Z-pVGyZ1vMBhUfYH@ryzen \
--to=cassel@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dlemoal@kernel.org \
--cc=john.g.garry@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=liyihang9@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=prime.zeng@hisilicon.com \
--cc=yangxingui@huawei.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