Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Sagi Grimberg <sagi@grimberg.me>,
	Caleb Sander Mateos <csander@purestorage.com>,
	Leon Romanovsky <leon@kernel.org>,
	linux-nvme@lists.infradead.org
Subject: Re: misc cleanups for nvme-pci
Date: Tue, 13 May 2025 09:34:36 -0600	[thread overview]
Message-ID: <aCNmjMm5aYQFE91s@kbusch-mbp> (raw)
In-Reply-To: <20250513070025.830930-1-hch@lst.de>

On Tue, May 13, 2025 at 09:00:16AM +0200, Christoph Hellwig wrote:
> this has misc cleanups for the nvme-pci I/O code.  Most of this was done
> as part of the new DMA API work.  Which then clashed with the per-node
> dmapools, so I'll try to get it out now instead of having to do another
> rebase.  As part of that this also includes minor tidyups for the new code
> from the per-node dmapools.

Series looks good. Just a minor optimization suggestion from me for
patch 5, and commit log issue Kanchan mentioned for patch 2.

Reviewed-by: Keith Busch <kbusch@kernel.org>


      parent reply	other threads:[~2025-05-13 15:38 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13  7:00 misc cleanups for nvme-pci Christoph Hellwig
2025-05-13  7:00 ` [PATCH 1/7] nvme-pci: don't try to use SGLs for metadata on the admin queue Christoph Hellwig
2025-05-13  7:28   ` Leon Romanovsky
2025-05-13  7:39     ` Christoph Hellwig
2025-05-13  7:45       ` Leon Romanovsky
2025-05-13  7:47         ` Christoph Hellwig
2025-05-13  7:51           ` Leon Romanovsky
2025-05-13  7:00 ` [PATCH 2/7] nvme-pci: store aborted state in flags variable Christoph Hellwig
2025-05-13 14:13   ` Kanchan Joshi/Kanchan Joshi
2025-05-14  0:44     ` Caleb Sander Mateos
2025-05-14  5:06     ` Christoph Hellwig
2025-05-13  7:00 ` [PATCH 3/7] nvme-pci: remove struct nvme_descriptor Christoph Hellwig
2025-05-13 14:15   ` Kanchan Joshi/Kanchan Joshi
2025-05-14  1:07   ` Caleb Sander Mateos
2025-05-14  5:15     ` Christoph Hellwig
2025-05-13  7:00 ` [PATCH 4/7] nvme-pci: rename the descriptor pools Christoph Hellwig
2025-05-13  7:35   ` Leon Romanovsky
2025-05-13 14:16   ` Kanchan Joshi/Kanchan Joshi
2025-05-14  1:03   ` Caleb Sander Mateos
2025-05-13  7:00 ` [PATCH 5/7] nvme-pci: use a better encoding for small prp pool allocations Christoph Hellwig
2025-05-13  7:39   ` Leon Romanovsky
2025-05-13  7:40     ` Christoph Hellwig
2025-05-13  7:49       ` Leon Romanovsky
2025-05-13 14:49   ` Kanchan Joshi/Kanchan Joshi
2025-05-13 15:06   ` Keith Busch
2025-05-14  5:12     ` Christoph Hellwig
2025-05-14 13:06       ` Keith Busch
2025-05-14 14:00         ` Christoph Hellwig
2025-05-14 17:48     ` Caleb Sander Mateos
2025-05-14 17:47   ` Caleb Sander Mateos
2025-05-13  7:00 ` [PATCH 6/7] nvme-pci: add a symolic name for the small pool size Christoph Hellwig
2025-05-13 14:51   ` Kanchan Joshi/Kanchan Joshi
2025-05-14 18:24   ` Caleb Sander Mateos
2025-05-13  7:00 ` [PATCH 7/7] nvme-pci: use struct_size for allocation struct nvme_dev Christoph Hellwig
2025-05-13  7:20   ` Leon Romanovsky
2025-05-13 14:54   ` Kanchan Joshi/Kanchan Joshi
2025-05-14 18:28   ` Caleb Sander Mateos
2025-05-13 15:34 ` 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=aCNmjMm5aYQFE91s@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=csander@purestorage.com \
    --cc=hch@lst.de \
    --cc=leon@kernel.org \
    --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