From: Jens Axboe <axboe@kernel.dk>
To: Daniel Gomez <da.gomez@kernel.org>, Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
Kanchan Joshi <joshi.k@samsung.com>,
Leon Romanovsky <leon@kernel.org>,
Nitesh Shetty <nj.shetty@samsung.com>,
Logan Gunthorpe <logang@deltatee.com>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: new DMA API conversion for nvme-pci v3
Date: Fri, 27 Jun 2025 08:56:32 -0600 [thread overview]
Message-ID: <42d8df98-65c7-4a4f-b931-ea32fe357fbf@kernel.dk> (raw)
In-Reply-To: <cddf9f29-c2e1-4b9c-b3b7-c64e3a513bf4@kernel.org>
On 6/27/25 1:37 AM, Daniel Gomez wrote:
> On 25/06/2025 18.38, Jens Axboe wrote:
>>
>> On Wed, 25 Jun 2025 13:34:57 +0200, Christoph Hellwig wrote:
>>> this series converts the nvme-pci driver to the new IOVA-based DMA API
>>> for the data path.
>>>
>>> Chances since v2:
>>> - fix handling of sgl_threshold=0
>>>
>>> Chances since v1:
>>> - minor cleanups to the block dma mapping helpers
>>> - fix the metadata SGL supported check for bisectability
>>> - fix SGL threshold check
>>> - fix/simplify metadata SGL force checks
>>>
>>> [...]
>>
>> Applied, thanks!
>>
>> [1/8] block: don't merge different kinds of P2P transfers in a single bio
>> commit: 226d6099402d8de166af60b2794fc198360d98fb
>> [2/8] block: add scatterlist-less DMA mapping helpers
>> commit: d6c12c69ef4fa33e32ceda4a53991ace01401cd9
>> [3/8] nvme-pci: refactor nvme_pci_use_sgls
>> commit: 07c81cbf438b769e0d673be3b5c021a424a4dc6f
>> [4/8] nvme-pci: merge the simple PRP and SGL setup into a common helper
>> commit: 06cae0e3f61c4c1ef18726b817bbb88c29f81e57
>> [5/8] nvme-pci: remove superfluous arguments
>> commit: 07de960ac7577662c68f1d21bd4907b8dfc790c4
>> [6/8] nvme-pci: convert the data mapping to blk_rq_dma_map
>> commit: 235118de382d6545d3822ead0571a05e017ed8f1
>> [7/8] nvme-pci: replace NVME_MAX_KB_SZ with NVME_MAX_BYTE
>> commit: d1df6bd4c551110e0d1b06ee85c7bca057439d28
>> [8/8] nvme-pci: rework the build time assert for NVME_MAX_NR_DESCRIPTORS
>> commit: 0c34198a16a88878aba455bebe157037c9ab52c5
>>
>> Best regards,
>
> Do you still accept new tags/trailers?
Even if they don't always end up in the git tree, please do provide
them. This thread is linked from there anyway, so it still provides
value.
--
Jens Axboe
next prev parent reply other threads:[~2025-06-27 14:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 11:34 new DMA API conversion for nvme-pci v3 Christoph Hellwig
2025-06-25 11:34 ` [PATCH 1/8] block: don't merge different kinds of P2P transfers in a single bio Christoph Hellwig
2025-06-25 11:34 ` [PATCH 2/8] block: add scatterlist-less DMA mapping helpers Christoph Hellwig
2025-06-25 11:35 ` [PATCH 3/8] nvme-pci: refactor nvme_pci_use_sgls Christoph Hellwig
2025-06-25 16:03 ` Keith Busch
2025-06-25 11:35 ` [PATCH 4/8] nvme-pci: merge the simple PRP and SGL setup into a common helper Christoph Hellwig
2025-06-25 11:35 ` [PATCH 5/8] nvme-pci: remove superfluous arguments Christoph Hellwig
2025-06-25 11:35 ` [PATCH 6/8] nvme-pci: convert the data mapping to blk_rq_dma_map Christoph Hellwig
2025-06-25 11:35 ` [PATCH 7/8] nvme-pci: replace NVME_MAX_KB_SZ with NVME_MAX_BYTE Christoph Hellwig
2025-06-25 11:35 ` [PATCH 8/8] nvme-pci: rework the build time assert for NVME_MAX_NR_DESCRIPTORS Christoph Hellwig
2025-06-25 16:38 ` new DMA API conversion for nvme-pci v3 Jens Axboe
2025-06-27 7:37 ` Daniel Gomez
2025-06-27 14:56 ` Jens Axboe [this message]
2025-06-27 17:53 ` Chaitanya Kulkarni
2025-06-26 15:33 ` Chaitanya Kulkarni
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=42d8df98-65c7-4a4f-b931-ea32fe357fbf@kernel.dk \
--to=axboe@kernel.dk \
--cc=da.gomez@kernel.org \
--cc=hch@lst.de \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=logang@deltatee.com \
--cc=nj.shetty@samsung.com \
--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