linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wei Huang <wei.huang2@amd.com>
To: lsf-pc@lists.linux-foundation.org
Cc: 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
Subject: [LSF/MM/BPF TOPIC] Enabling Smart Data Stream Accelerator Support for Linux
Date: Fri, 31 Jan 2025 11:53:07 -0600	[thread overview]
Message-ID: <f3212aef-ebc4-4447-9cae-7bc9b528334e@amd.com> (raw)

Hi All,

I want to proposal a talk for the LSFMMBPF conference: Enabling Smart 
Data Stream Accelerator (SDXI) Support for Linux.

The smart data stream accelerator (SDXI) is an industry standard [1] 
that provides various advanced capabilities, such as offloading DMA 
operations, supporting user-space addresses, and offering other advanced 
data processing features. With the integration of SDXI into a SoC, DMA 
offloading can now be supported across different address spaces. This 
talk focuses on a software design which enables comprehensive SDXI 
support across multiple software layers in the Linux Kernel. These 
interfaces not only facilitate SDXI hardware management but also allow 
kernel space subsystems and user space applications to directly own and 
control SDXI hardware under the protection of IOMMU.

To illustrate the practical applications of SDXI, Red Hat and AMD 
developed a user-space library that leverages the SDXI driver interface, 
demonstrating various use cases, such as memory operation offloading, in 
both bare-metal and virtual environments.

The prototype device driver [2] and user-space library are available for 
testing. We continue to work on the improvement of both components and 
plan to upstream the device driver soon.

== DISCUSSION ==
At this conference, we plan to discuss with the community on:

1) Use Cases
* Linux DMA engine
* Kernel task offloading (e.g., bulk copying)
* QoS and kernel perf integration
* New use cases

2) User-Space API Interface
* IOCTL proposal
* Security control
* User-space app integration

3) Virtualization Support
* Progress & current status
* Challenges

== REFERENCES ==
[1] SDXI 1.0 specification, https://www.snia.org/sdxi
[2] SDXI device driver, https://github.com/AMDESE/linux-sdxi

Thanks,
-Wei



             reply	other threads:[~2025-01-31 17:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-31 17:53 Wei Huang [this message]
2025-02-03 10:13 ` Jonathan Cameron
2025-02-03 14:23   ` Jason Gunthorpe
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=f3212aef-ebc4-4447-9cae-7bc9b528334e@amd.com \
    --to=wei.huang2@amd.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=shivankg@amd.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