[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251117-nvme-phys-types-v2-0-c75a60a2c468@nvidia.com>
Date: Mon, 17 Nov 2025 21:22:42 +0200
From: Leon Romanovsky <leon@...nel.org>
To: Jens Axboe <axboe@...nel.dk>,
Keith Busch <kbusch@...nel.org>,
Christoph Hellwig <hch@....de>,
Sagi Grimberg <sagi@...mberg.me>
Cc: linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-nvme@...ts.infradead.org,
Chaitanya Kulkarni <kch@...dia.com>
Subject: [PATCH v2 0/2] block: Generalize physical entry definition
Changelog:
v2:
* Added Chaitanya's Reviewed-by tags.
* Removed explicit casting from size_t to unsigned int.
v1: https://patch.msgid.link/20251115-nvme-phys-types-v1-0-c0f2e5e9163d@kernel.org
--------------------------------------------------------------------------------
The block layer code is declared "struct phys_vec" entry which describes
contiguous chunk of physical memory. That definition is useful for all
possible users of DMA physical address-based API.
This series changes NVMe code to support larger chunks of memory by changing
length field from u32 to be size_t, which will be u64 on 64-bits platforms,
and promotes "struct phys_vec" to general place.
---
Leon Romanovsky (2):
nvme-pci: Use size_t for length fields to handle larger sizes
types: move phys_vec definition to common header
block/blk-mq-dma.c | 11 +++++------
drivers/nvme/host/pci.c | 4 ++--
include/linux/types.h | 5 +++++
3 files changed, 12 insertions(+), 8 deletions(-)
---
base-commit: 5674abb82e2b74205a6a5cd1ffd79a3ba48a469d
change-id: 20251030-nvme-phys-types-988893249454
Best regards,
--
Leon Romanovsky <leonro@...dia.com>
Powered by blists - more mailing lists