linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: "Ewan D. Milne" <emilne@redhat.com>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: scsi_transport_fc: Change to use per-rport devloss_work_q
Date: Tue, 8 Jul 2025 10:22:37 +0200	[thread overview]
Message-ID: <dbf131f9-f28b-442c-8047-c0d8c32ab53c@suse.de> (raw)
In-Reply-To: <20250707202225.1203189-1-emilne@redhat.com>

On 7/7/25 22:22, Ewan D. Milne wrote:
> Configurations with large numbers of FC rports per host instance are taking a
> very long time to complete all devloss work.  Increase potential parallelism
> by using a per-rport devloss_work_q for dev_loss_work and fast_io_fail_work.
> 
> Signed-off-by: Ewan D. Milne <emilne@redhat.com>
> ---
>   drivers/scsi/scsi_transport_fc.c | 70 ++++++++++++++++++--------------
>   include/scsi/scsi_transport_fc.h |  5 +--
>   2 files changed, 42 insertions(+), 33 deletions(-)
> 

Reviewed-by: Hannes Reinecke <hare@suse.de>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                  Kernel Storage Architect
hare@suse.de                                +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich

  reply	other threads:[~2025-07-08  8:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-07 20:22 [PATCH] scsi: scsi_transport_fc: Change to use per-rport devloss_work_q Ewan D. Milne
2025-07-08  8:22 ` Hannes Reinecke [this message]
2025-07-14 17:21 ` Martin K. Petersen
2025-07-22  3:46 ` 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=dbf131f9-f28b-442c-8047-c0d8c32ab53c@suse.de \
    --to=hare@suse.de \
    --cc=emilne@redhat.com \
    --cc=linux-scsi@vger.kernel.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 NNTP newsgroup(s).