All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Damir Chanyshev <conflict342@gmail.com>
Cc: linux-pci@vger.kernel.org, Logan Gunthorpe <logang@deltatee.com>,
	"Michael J. Ruhl" <michael.j.ruhl@intel.com>
Subject: Re: P2PDMA support status for the sappire rapids+
Date: Tue, 8 Apr 2025 10:06:23 -0500	[thread overview]
Message-ID: <20250408150623.GA232275@bhelgaas> (raw)
In-Reply-To: <CAAUwoOjXGzaTQ4Dbx3wcMOiy484Sjd4Vv1=ZDiVrYvCEaNiRcA@mail.gmail.com>

[+cc Logan, Michael]

On Tue, Apr 08, 2025 at 05:48:16PM +0300, Damir Chanyshev wrote:
> Hello experts!
> First thank you so much for everything.
> 
> I have a question regarding p2pdma support, I am not an expert in the
> kernel subsystems, please pardon my stupidity.
> While investigating performance opportunities, I stumbled with dma
> between cpu root complex and pcie switch root complex. And found white
> list for the Intel platforms [1]
> 
> Typical topology looks like this rdma nic<>cpu<>pcie switch<>gpu/xpu,
> for each socket.
> Questions:
> List not updated because new hardware doesn't support this feature?
> (For example abandoned for the CXL3+ )
> Or just not tested for the new platforms?
> 
> [1]
> https://lore.kernel.org/all/20220209162801.7647-1-michael.j.ruhl@intel.com/T/#m3f4e4194770274c2873a130ad684a74469038585

The pci_p2pdma_whitelist[] is only updated when somebody tests a
platform and determines that its RC can route peer-to-peer
transactions between separate Root Ports.  This routing is not
required by the PCIe spec, so we can't assume that all platforms
support it.

From PCIe r6.0, sec 1.3.1:

  The capability to route peer-to-peer transactions between hierarchy
  domains through an RC is optional and implementation dependent.

Bjorn

  reply	other threads:[~2025-04-08 15:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 14:48 P2PDMA support status for the sappire rapids+ Damir Chanyshev
2025-04-08 15:06 ` Bjorn Helgaas [this message]
2025-04-08 15:14   ` Damir Chanyshev
2025-04-08 15:28     ` Lukas Wunner
2025-04-08 16:25       ` Logan Gunthorpe
2025-04-08 15:11 ` Lukas Wunner

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=20250408150623.GA232275@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=conflict342@gmail.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=michael.j.ruhl@intel.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.