From: Sagi Grimberg <sagi@grimberg.me>
To: Kamaljit Singh <Kamaljit.Singh1@wdc.com>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: "kbusch@kernel.org" <kbusch@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: WQ_UNBOUND workqueue warnings from multiple drivers
Date: Thu, 9 May 2024 09:36:28 +0300 [thread overview]
Message-ID: <dfb9074c-d019-4a19-83eb-00d93da8dada@grimberg.me> (raw)
In-Reply-To: <BYAPR04MB415180536421C9B8326D6A30BCE52@BYAPR04MB4151.namprd04.prod.outlook.com>
On 09/05/2024 2:16, Kamaljit Singh wrote:
> Sagi,
>
>> Does this happen with a 90-%100% read workload?
> Yes, we’ve now seen it with 100% reads as well. Here’s the Medusa cmd we used. I’ve removed the devices for brevity.
> sudo /opt/medusa_labs/test_tools/bin/maim 20g -b8K -Q128 -Y1 -M30 --full-device -B3 -r -d900000 <device_list>
>
> We saw the original issue with the upstream kernel v6.6.21. But now we’re also seeing it with Ubuntu 24.04 (kernel 6.8.0-31-generic), where IOs are timing out and forcing connection drops.
Thanks for the info.
>
>
>> Question, are you working with a Linux controller?
> No, with our ASIC (NVMe Fabrics bridge).
>
>> what is the ctrl ioccsz?
> ioccsz : 4
I see, what is the mdts? and what are the r2t lengths the controller is
sending to the host?
prev parent reply other threads:[~2024-05-09 6:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 22:33 WQ_UNBOUND workqueue warnings from multiple drivers Kamaljit Singh
2024-03-20 9:11 ` Sagi Grimberg
2024-03-21 17:36 ` Chaitanya Kulkarni
2024-04-02 23:50 ` Kamaljit Singh
2024-04-07 20:08 ` Sagi Grimberg
2024-05-08 23:16 ` Kamaljit Singh
2024-05-09 6:36 ` Sagi Grimberg [this message]
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=dfb9074c-d019-4a19-83eb-00d93da8dada@grimberg.me \
--to=sagi@grimberg.me \
--cc=Kamaljit.Singh1@wdc.com \
--cc=chaitanyak@nvidia.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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 read-only IMAP folder(s) and NNTP newsgroup(s).