From: Keith Busch <kbusch@fb.com>
To: <linux-nvme@lists.infradead.org>
Cc: <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Chaitanya Kulkarni <kch@nvidia.com>
Subject: [PATCHv3 4/4] nvme-pci: move iod dma_len fill gaps
Date: Tue, 6 Sep 2022 09:07:38 -0700 [thread overview]
Message-ID: <20220906160738.2289621-5-kbusch@fb.com> (raw)
In-Reply-To: <20220906160738.2289621-1-kbusch@fb.com>
From: Keith Busch <kbusch@kernel.org>
The 32-bit field, dma_len, packs better in the iod struct above the
dma_addr_t on 64-bit systems.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Signed-off-by: Keith Busch <kbusch@kernel.org>
---
drivers/nvme/host/pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 7339efc4cb86..4652df0fbaa9 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -229,8 +229,8 @@ struct nvme_iod {
bool use_sgl;
bool aborted;
s8 nr_allocations; /* PRP list pool allocations. 0 means small pool in use */
- dma_addr_t first_dma;
unsigned int dma_len; /* length of single DMA segment mapping */
+ dma_addr_t first_dma;
dma_addr_t meta_dma;
struct sg_table sgt;
};
--
2.30.2
next prev parent reply other threads:[~2022-09-06 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 16:07 [PATCHv3 0/4] Keith Busch
2022-09-06 16:07 ` [PATCHv3 1/4] nvme-pci: remove nvme_queue from nvme_iod Keith Busch
2022-09-06 16:07 ` [PATCHv3 2/4] nvme-pci: iod's 'aborted' is a bool Keith Busch
2022-09-06 16:07 ` [PATCHv3 3/4] nvme-pci: iod npages fits in s8 Keith Busch
2022-09-06 16:07 ` Keith Busch [this message]
2022-09-07 6:48 ` [PATCHv3 0/4] Christoph Hellwig
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=20220906160738.2289621-5-kbusch@fb.com \
--to=kbusch@fb.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.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