public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Pranjal Shrivastava <praan@google.com>
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
	linux-nvme@lists.infradead.org, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org, kch@nvidia.com
Subject: Re: [RFC PATCH v2] nvme: enable PCI P2PDMA support for RDMA transport
Date: Thu, 2 Apr 2026 16:03:04 +0000	[thread overview]
Message-ID: <ac6TOJMXtmBzNL_X@google.com> (raw)
In-Reply-To: <20260402073001.2039625-1-shivajikant@google.com>

On Thu, Apr 02, 2026 at 07:30:01AM +0000, Shivaji Kant wrote:
> Enable BLK_FEAT_PCI_P2PDMA on the NVMe when the underlying
> RDMA controller supports it.
> 
> This patch depends on the PCI P2PDMA support added in this
> patch [1].
> 
> Suggested-by: Pranjal Shrivastava <praan@google.com>
> Signed-off-by: Shivaji Kant <shivajikant@google.com>
> ---
> [1] https://lore.kernel.org/all/20260323234416.46944-3-kch@nvidia.com/
> ---
>  drivers/nvme/host/rdma.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/drivers/nvme/host/rdma.c b/drivers/nvme/host/rdma.c
> index 35c0822edb2d..09eefd7c3ff4 100644
> --- a/drivers/nvme/host/rdma.c
> +++ b/drivers/nvme/host/rdma.c
> @@ -2189,6 +2189,13 @@ static void nvme_rdma_reset_ctrl_work(struct work_struct *work)
>  	nvme_rdma_reconnect_or_remove(ctrl, ret);
>  }
>  
> +static bool nvme_rdma_supports_pci_p2pdma(struct nvme_ctrl *ctrl)
> +{
> +	struct nvme_rdma_ctrl *r_ctrl = to_rdma_ctrl(ctrl);
> +
> +	return ib_dma_pci_p2p_dma_supported(r_ctrl->device->dev);
> +}
> +
>  static const struct nvme_ctrl_ops nvme_rdma_ctrl_ops = {
>  	.name			= "rdma",
>  	.module			= THIS_MODULE,
> @@ -2203,6 +2210,7 @@ static const struct nvme_ctrl_ops nvme_rdma_ctrl_ops = {
>  	.get_address		= nvmf_get_address,
>  	.stop_ctrl		= nvme_rdma_stop_ctrl,
>  	.get_virt_boundary	= nvme_get_virt_boundary,
> +	.supports_pci_p2pdma	= nvme_rdma_supports_pci_p2pdma,
>  };
>  

+Chaitanya.

Hi Chaitanya, would you like to pick this up with your v2 for the
multipath p2p enablement series [1] ?

For the changes (with Chaitanya's mpath patch):
Reviewed-by: Pranjal Shrivastava <praan@google.com>

Thanks,
Praan

[1] https://lore.kernel.org/all/20260323234416.46944-3-kch@nvidia.com/


  reply	other threads:[~2026-04-02 16:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-02  7:30 [RFC PATCH v2] nvme: enable PCI P2PDMA support for RDMA transport Shivaji Kant
2026-04-02 16:03 ` Pranjal Shrivastava [this message]
2026-04-04  5:16 ` Shivaji Kant
2026-04-06  5:41 ` Christoph Hellwig
     [not found] ` <azabfvzjn4juc77xdq6qhszd6py6hkb35jgi2xymplpnkj5ra4@vpjpaoeenvlu>
2026-04-06  9:15   ` Shivaji Kant

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=ac6TOJMXtmBzNL_X@google.com \
    --to=praan@google.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=kch@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-rdma@vger.kernel.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