Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
	Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH v2] nvmet: pci-epf: Keep completion queues mapped
Date: Thu, 13 Mar 2025 11:15:47 -0600	[thread overview]
Message-ID: <Z9MSw53Bq2hvvMYD@kbusch-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20250313082218.1444073-1-dlemoal@kernel.org>

On Thu, Mar 13, 2025 at 05:22:18PM +0900, Damien Le Moal wrote:
> Instead of mapping and unmapping the completion queues memory to the
> host PCI address space whenever nvmet_pci_epf_cq_work() is called, map
> a completion queue to the host PCI address space when the completion
> queue is created with nvmet_pci_epf_create_cq() and unmap it when the
> completion queue is deleted with nvmet_pci_epf_delete_cq().
> 
> This removes the completion queue mapping/unmapping from
> nvmet_pci_epf_cq_work() and significantly increases performance. For
> a single job 4K random read QD=1 workload, the IOPS is increased from
> 23 KIOPS to 25 KIOPS. Some significant throughput increasde for high
> queue depth and large IOs workloads can also be seen.
> 
> Since the functions nvmet_pci_epf_map_queue() and
> nvmet_pci_epf_unmap_queue() are called respectively only from
> nvmet_pci_epf_create_cq() and nvmet_pci_epf_delete_cq(), these functions
> are removed and open-coded in their respective call sites.

Thanks, applied to nvme-6.15.


      parent reply	other threads:[~2025-03-13 17:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13  8:22 [PATCH v2] nvmet: pci-epf: Keep completion queues mapped Damien Le Moal
2025-03-13  8:29 ` Christoph Hellwig
2025-03-13 17:15 ` Keith Busch [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=Z9MSw53Bq2hvvMYD@kbusch-mbp.dhcp.thefacebook.com \
    --to=kbusch@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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