From: Christoph Hellwig <hch@infradead.org>
To: "Melanie Plageman (Microsoft)" <melanieplageman@gmail.com>
Cc: tyreld@linux.ibm.com, linux-hyperv@vger.kernel.org,
mst@redhat.com, benh@kernel.crashing.org, mikelley@microsoft.com,
R-QLogic-Storage-Upstream@marvell.com, paulus@samba.org,
wei.liu@kernel.org, sthemmin@microsoft.com,
linux-scsi@vger.kernel.org, mpe@ellerman.id.au,
sathya.prakash@broadcom.com, decui@microsoft.com,
kashyap.desai@broadcom.com, njavali@marvell.com,
MPT-FusionLinux.pdl@broadcom.com, haiyangz@microsoft.com,
mpi3mr-linuxdrv.pdl@broadcom.com,
suganath-prabu.subramani@broadcom.com, jejb@linux.ibm.com,
john.garry@huawei.com, stefanha@redhat.com,
storagedev@microchip.com,
virtualization@lists.linux-foundation.org,
megaraidlinux.pdl@broadcom.com, sreekanth.reddy@broadcom.com,
martin.petersen@oracle.com,
shivasharan.srikanteshwara@broadcom.com,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
sumit.saxena@broadcom.com, andres@anarazel.de,
pbonzini@redhat.com, don.brace@microchip.com
Subject: Re: [PATCH RFC v1 0/5] Add SCSI per device tagsets
Date: Fri, 18 Feb 2022 23:37:03 -0800 [thread overview]
Message-ID: <YhCeHweaO5ugY5aC@infradead.org> (raw)
In-Reply-To: <20220218184157.176457-1-melanieplageman@gmail.com>
On Fri, Feb 18, 2022 at 06:41:52PM +0000, Melanie Plageman (Microsoft) wrote:
> Currently a single blk_mq_tag_set is associated with a Scsi_Host. When SCSI
> controllers are limited, attaching multiple devices to the same controller is
> required. In cloud environments with relatively high latency persistent storage,
> requiring all devices on a controller to share a single blk_mq_tag_set
> negatively impacts performance.
So add more controllers instead of completely breaking the architecture.
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
parent reply other threads:[~2022-02-19 7:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220218184157.176457-1-melanieplageman@gmail.com>]
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=YhCeHweaO5ugY5aC@infradead.org \
--to=hch@infradead.org \
--cc=MPT-FusionLinux.pdl@broadcom.com \
--cc=R-QLogic-Storage-Upstream@marvell.com \
--cc=andres@anarazel.de \
--cc=benh@kernel.crashing.org \
--cc=decui@microsoft.com \
--cc=don.brace@microchip.com \
--cc=haiyangz@microsoft.com \
--cc=jejb@linux.ibm.com \
--cc=john.garry@huawei.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=martin.petersen@oracle.com \
--cc=megaraidlinux.pdl@broadcom.com \
--cc=melanieplageman@gmail.com \
--cc=mikelley@microsoft.com \
--cc=mpe@ellerman.id.au \
--cc=mpi3mr-linuxdrv.pdl@broadcom.com \
--cc=mst@redhat.com \
--cc=njavali@marvell.com \
--cc=paulus@samba.org \
--cc=pbonzini@redhat.com \
--cc=sathya.prakash@broadcom.com \
--cc=shivasharan.srikanteshwara@broadcom.com \
--cc=sreekanth.reddy@broadcom.com \
--cc=stefanha@redhat.com \
--cc=sthemmin@microsoft.com \
--cc=storagedev@microchip.com \
--cc=suganath-prabu.subramani@broadcom.com \
--cc=sumit.saxena@broadcom.com \
--cc=tyreld@linux.ibm.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=wei.liu@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).