From: Bart Van Assche <bvanassche@acm.org>
To: "Martin K . Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
John Garry <john.g.garry@oracle.com>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH v2 0/5] Increase SCSI IOPS
Date: Fri, 21 Nov 2025 13:17:40 -0800 [thread overview]
Message-ID: <c7d42cdc-dbf8-4eda-9844-70755a728d2d@acm.org> (raw)
In-Reply-To: <20251117225205.2024479-1-bvanassche@acm.org>
On 11/17/25 2:51 PM, Bart Van Assche wrote:
> This patch series increases scsi_debug IOPS by 5% on my test setup by disabling
> SCSI budget management if it is not needed.
(replying to my own email)
The kernel test robot reported that this patch series introduces a hang
during LUN scanning for ATA devices. I have been able to reproduce this
hang in a VM. The root cause has been identified and a fix is under
test. I will post a new version of this patch series after testing has
finished.
Thanks,
Bart.
next prev parent reply other threads:[~2025-11-21 21:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 22:51 [PATCH v2 0/5] Increase SCSI IOPS Bart Van Assche
2025-11-17 22:52 ` [PATCH v2 1/5] block: Rename busy_tag_iter_fn into blk_mq_rq_iter_fn Bart Van Assche
2025-11-17 22:52 ` [PATCH v2 2/5] block: Introduce __blk_mq_tagset_iter() Bart Van Assche
2025-11-17 22:52 ` [PATCH v2 3/5] block: Introduce blk_mq_tagset_iter() Bart Van Assche
2025-11-17 22:52 ` [PATCH v2 4/5] scsi: core: Generalize scsi_device_busy() Bart Van Assche
2025-11-17 22:52 ` [PATCH v2 5/5] scsi: core: Improve IOPS in case of host-wide tags Bart Van Assche
2025-11-21 21:17 ` Bart Van Assche [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-24 18:21 [PATCH v2 0/5] Increase SCSI IOPS Bart Van Assche
2025-11-25 8:20 ` Niklas Cassel
2025-11-25 16:45 ` Bart Van Assche
2025-11-25 9:08 ` John Garry
2025-11-25 16:51 ` Bart Van Assche
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=c7d42cdc-dbf8-4eda-9844-70755a728d2d@acm.org \
--to=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).