From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Michael Margolin <mrgolin@amazon.com>,
Yonatan Nachum <ynachum@amazon.com>,
linux-rdma@vger.kernel.org, sleybo@amazon.com, matua@amazon.com,
gal.pressman@linux.dev, Yehuda Yitschak <yehuday@amazon.com>
Subject: Re: [PATCH for-next] RDMA/efa: Expose device P2P DMA support via device query
Date: Fri, 2 Oct 2026 11:52:41 -0300 [thread overview]
Message-ID: <20261002145241.GV1616761@nvidia.com> (raw)
In-Reply-To: <20261001155333.GP3401365@unreal>
On Thu, Oct 01, 2026 at 06:53:33PM +0300, Leon Romanovsky wrote:
> > Looked at Leon's patches and it does seem like the right place to expose
> > such peer relations. Although it wouldn't help with our immediate need,
> > maybe we can add a sysfs interface on top of Leon's patches to expose
> > the gathered accessiblity (and maybe also performance) information.
> >
> > Leon, what is your opinion on this?
>
> ACPI tables are available here /sys/firmware/acpi/tables/, this will
> include our new p2p HMAT extension.
ACPI is nice and general, but..
Doesn't AWS have something already to convay VM instance type
configuration information? That's pretty normal these days isn't it?
Jason
next prev parent reply other threads:[~2026-10-02 14:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 15:02 [PATCH for-next] RDMA/efa: Expose device P2P DMA support via device query Yonatan Nachum
2026-05-04 7:34 ` Jason Gunthorpe
2026-05-05 8:15 ` Yonatan Nachum
2026-05-05 15:40 ` Jason Gunthorpe
2026-09-23 16:38 ` Michael Margolin
2026-09-23 17:17 ` Jason Gunthorpe
2026-09-24 15:29 ` Michael Margolin
2026-09-24 18:22 ` Jason Gunthorpe
2026-09-24 19:30 ` Michael Margolin
2026-09-25 12:55 ` Jason Gunthorpe
2026-09-30 13:26 ` Michael Margolin
2026-10-01 15:53 ` Leon Romanovsky
2026-10-02 14:52 ` Jason Gunthorpe [this message]
2026-10-07 9:01 ` Michael Margolin
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=20261002145241.GV1616761@nvidia.com \
--to=jgg@nvidia.com \
--cc=gal.pressman@linux.dev \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matua@amazon.com \
--cc=mrgolin@amazon.com \
--cc=sleybo@amazon.com \
--cc=yehuday@amazon.com \
--cc=ynachum@amazon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox