From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sidong Yang <sidong.yang@furiosa.ai>
Cc: Jens Axboe <axboe@kernel.dk>,
Daniel Almeida <daniel.almeida@collabora.com>,
Caleb Sander Mateos <csander@purestorage.com>,
Benno Lossin <lossin@kernel.org>, Miguel Ojeda <ojeda@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
io-uring@vger.kernel.org
Subject: Re: [PATCH v4 0/5] Rust io_uring command abstraction for miscdevice
Date: Tue, 14 Apr 2026 18:20:52 +0200 [thread overview]
Message-ID: <2026041407-tubular-unhealthy-2a7f@gregkh> (raw)
In-Reply-To: <ad5e5cAmtL8GRo-s@sidongui-MacBookPro.local>
On Wed, Apr 15, 2026 at 12:36:05AM +0900, Sidong Yang wrote:
> > Yes, it must use the accel subsystem as that is the correct api for it.
>
> Thanks for the clarification.
>
> I will proceed with this uring_cmd Rust abstraction patch as is. Moving
> forward with our AI accelerator driver, I will look into implementing it
> using the accel subsystem and work on creating the necessary Rust
> abstractions for it.
Great.
> Since I am planning to adopt the accel subsystem, could you share some
> insights on the main benefits it provides for AI accelerators, or point me
> to any future roadmap/plans for the subsystem? This would be very helpful
> for my design and implementation.
It is the common api for all accelerator drivers that you must use if
you wish to have a Linux driver for this type of hardware. There should
be documentation in the kernel subsystem to read, and of course, there
are existing drivers using the api already. If you have specific
questions about the api, please ask on that mailing list.
thanks,
greg k-h
prev parent reply other threads:[~2026-04-14 16:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 13:59 Sidong Yang
2026-04-08 13:59 ` [PATCH v4 1/5] rust: bindings: add io_uring headers in bindings_helper.h Sidong Yang
2026-04-08 14:31 ` Miguel Ojeda
2026-04-09 1:20 ` Sidong Yang
2026-04-08 13:59 ` [PATCH v4 2/5] io_uring/cmd: zero-init pdu in io_uring_cmd_prep() to avoid UB Sidong Yang
2026-04-09 5:27 ` Greg Kroah-Hartman
2026-04-11 12:11 ` Sidong Yang
2026-04-08 14:00 ` [PATCH v4 3/5] rust: io_uring: introduce rust abstraction for io-uring cmd Sidong Yang
2026-04-08 14:00 ` [PATCH v4 4/5] rust: miscdevice: Add `uring_cmd` support Sidong Yang
2026-04-08 14:00 ` [PATCH v4 5/5] samples: rust: Add `uring_cmd` example to `rust_misc_device` Sidong Yang
2026-04-09 5:25 ` [PATCH v4 0/5] Rust io_uring command abstraction for miscdevice Greg Kroah-Hartman
2026-04-11 12:16 ` Sidong Yang
2026-04-11 12:27 ` Greg Kroah-Hartman
2026-04-14 15:36 ` Sidong Yang
2026-04-14 16:20 ` Greg Kroah-Hartman [this message]
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=2026041407-tubular-unhealthy-2a7f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=daniel.almeida@collabora.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sidong.yang@furiosa.ai \
/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
all inboxes | Powered by JetHome®