From: Jason Gunthorpe <jgg@nvidia.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: Wei Huang <wei.huang2@amd.com>,
lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
Don Dutile <ddutile@redhat.com>, Joel Savitz <jsavitz@redhat.com>,
"Moyes, William" <William.Moyes@amd.com>,
"Iyer, Shyam" <Shyam.Iyer@dell.com>,
"Lynch, Nathan" <Nathan.Lynch@amd.com>,
mel.gorman@gmail.com, santosh.shukla@amd.com, "Suthikulpanit,
Suravee" <Suravee.Suthikulpanit@amd.com>,
shivankg@amd.com, Michael.Day@amd.com,
Zhangfei Gao <zhangfei.gao@linaro.org>,
Zhou Wang <wangzhou1@hisilicon.com>,
Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
Subject: Re: [LSF/MM/BPF TOPIC] Enabling Smart Data Stream Accelerator Support for Linux
Date: Mon, 3 Feb 2025 10:23:20 -0400 [thread overview]
Message-ID: <20250203142320.GU5556@nvidia.com> (raw)
In-Reply-To: <20250203101323.00001e6e@huawei.com>
On Mon, Feb 03, 2025 at 10:13:23AM +0000, Jonathan Cameron wrote:
> Lots of topics and hints at interesting areas, but I'd like to see more
> details to understand how this maps to other data moving / reorganizing
> accelerators. Whilst SDXI looks like a good and feature rich spec,
> I'm curious what is fundamentally new? Perhaps it is just the
> right time to improve functionality for DMA engines in general.
It looks quite alot like Intel's IDXD to me, which seems to have alot
of overlap.
> > [2] SDXI device driver, https://github.com/AMDESE/linux-sdxi
Sorry, but a never posted branch based on an v6.6 kernel using alot of
obsoleted and removed iommu APIs doesn't seem like LSF/MM content to
me. LSF/MM is supposed to be a problem solving conference, you should
ideally have something in active discussion on the mailing list with
an unresolved problem to talk about.
Jason
next prev parent reply other threads:[~2025-02-03 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 17:53 Wei Huang
2025-02-03 10:13 ` Jonathan Cameron
2025-02-03 14:23 ` Jason Gunthorpe [this message]
2025-02-04 0:59 ` Wei Huang
2025-02-04 0:52 ` Wei Huang
2025-02-04 4:19 ` [Lsf-pc] " Dan Williams
2025-02-04 7:59 ` 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=20250203142320.GU5556@nvidia.com \
--to=jgg@nvidia.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Michael.Day@amd.com \
--cc=Nathan.Lynch@amd.com \
--cc=Shyam.Iyer@dell.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=William.Moyes@amd.com \
--cc=ddutile@redhat.com \
--cc=jsavitz@redhat.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mel.gorman@gmail.com \
--cc=santosh.shukla@amd.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=shivankg@amd.com \
--cc=wangzhou1@hisilicon.com \
--cc=wei.huang2@amd.com \
--cc=zhangfei.gao@linaro.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