All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Keith Busch <kbusch@meta.com>
Cc: linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
	hch@lst.de, axboe@kernel.dk, martin.petersen@oracle.com,
	jgg@nvidia.com, Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCHv2 2/2] blk-mq-dma: bring back p2p request flags
Date: Wed, 3 Sep 2025 11:20:30 +0300	[thread overview]
Message-ID: <20250903082030.GA5608@unreal> (raw)
In-Reply-To: <20250902200121.3665600-3-kbusch@meta.com>

On Tue, Sep 02, 2025 at 01:01:21PM -0700, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
> 
> We need to consider data and metadata dma mapping types separately. The
> request and bio integrity payload have enough flag bits to internally
> track the mapping type for each. Use these so the caller doesn't need to
> track them, and provide separete request and integrity helpers to the
> common code. This will make it easier to scale new mappings, like the
> proposed MMIO attribute, without burdening the caller to track such
> things.
> 
> Signed-off-by: Keith Busch <kbusch@kernel.org>
> ---
>  block/blk-mq-dma.c            |  4 ++++
>  drivers/nvme/host/pci.c       | 21 ++++-----------------
>  include/linux/bio-integrity.h |  1 +
>  include/linux/blk-integrity.h | 14 ++++++++++++++
>  include/linux/blk-mq-dma.h    | 11 +++++++++--
>  include/linux/blk_types.h     |  2 ++
>  6 files changed, 34 insertions(+), 19 deletions(-)
> 

Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>

  parent reply	other threads:[~2025-09-03  8:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02 20:01 [PATCHv2 0/2] blk-mq-dma: p2p cleanups and integrity fixup Keith Busch
2025-09-02 20:01 ` [PATCHv2 1/2] blk-integrity: enable p2p source and destination Keith Busch
2025-09-02 20:01 ` [PATCHv2 2/2] blk-mq-dma: bring back p2p request flags Keith Busch
2025-09-03  6:09   ` Christoph Hellwig
2025-09-03  8:20   ` Leon Romanovsky [this message]
2025-09-03 11:02   ` kernel test robot
2025-09-03  7:55 ` [PATCHv2 0/2] blk-mq-dma: p2p cleanups and integrity fixup Martin K. Petersen

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=20250903082030.GA5608@unreal \
    --to=leon@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=jgg@nvidia.com \
    --cc=kbusch@kernel.org \
    --cc=kbusch@meta.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=martin.petersen@oracle.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.