From: "Danilo Krummrich" <dakr@kernel.org>
To: "Boqun Feng" <boqun.feng@gmail.com>
Cc: "Philipp Stanner" <phasta@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>, "Will Deacon" <will@kernel.org>,
"Waiman Long" <longman@redhat.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <nick.desaulniers+lkml@gmail.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Asahi Lina" <lina+kernel@asahilina.net>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Tamir Duberstein" <tamird@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"FUJITA Tomonori" <fujita.tomonori@gmail.com>,
"Krishna Ketan Rai" <prafulrai522@gmail.com>,
"Lyude Paul" <lyude@redhat.com>,
"Mitchell Levy" <levymitchell0@gmail.com>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
llvm@lists.linux.dev, dri-devel@lists.freedesktop.org
Subject: Re: [RFC PATCH] rust: sync: Add dma_fence abstractions
Date: Sun, 28 Sep 2025 17:20:59 +0200 [thread overview]
Message-ID: <DD4JABIXIZLT.120ZAR2GODC1O@kernel.org> (raw)
In-Reply-To: <aNa7BDpKS2KA__4M@tardis.local>
On Fri Sep 26, 2025 at 6:10 PM CEST, Boqun Feng wrote:
> I missed this part, and I don't think kernel::sync is where dma_fence
> should be, as kernel::sync is mostly for the basic synchronization
> between threads/irqs. dma_fence is probably better to be grouped with
> dma-buf and other dma related primitives. Maybe in kernel::dma? Like:
I agree, kernel::sync may be a bit misleading.
> rust/kernel/dma.rs
> rust/kernel/dma/dma_buf.rs
> rust/kernel/dma/dma_fence.rs
>
> Thoughts? Miguel, Greg, Danilo and Lyude, any idea or suggestion?
To me it depends on if we want to maintain the code under a global
DMA MAPPING & SCATTERLIST API entry or if it will just be added to the
DMA BUFFER SHARING FRAMEWORK entry.
In case of the latter I'd go for rust/kernel/dma-buf/, analogous to
drivers/dma-buf/. (Though, I'm not sure why this is under drivers/, there's
nothing like dma-buf drivers; I think kernel/dma/ would have been the better
fit.)
In any case, the target tree would probably be the drm-rust tree.
prev parent reply other threads:[~2025-09-28 15:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 12:30 [RFC PATCH] rust: sync: Add dma_fence abstractions Philipp Stanner
2025-09-18 13:11 ` Christian König
2025-09-18 13:53 ` Philipp Stanner
2025-09-18 13:52 ` Boqun Feng
2025-09-26 8:48 ` Philipp Stanner
2025-09-26 15:44 ` Boqun Feng
2025-09-26 16:10 ` Boqun Feng
2025-09-27 9:01 ` Philipp Stanner
2025-09-27 13:33 ` Boqun Feng
2025-09-28 14:34 ` Christian König
2025-09-28 15:26 ` Philipp Stanner
2025-09-28 15:57 ` Christian König
2025-09-27 12:14 ` Miguel Ojeda
2025-09-27 14:03 ` Boqun Feng
2025-09-28 15:20 ` Danilo Krummrich [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=DD4JABIXIZLT.120ZAR2GODC1O@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=christian.koenig@amd.com \
--cc=daniel.almeida@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=justinstitt@google.com \
--cc=levymitchell0@gmail.com \
--cc=lina+kernel@asahilina.net \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=longman@redhat.com \
--cc=lossin@kernel.org \
--cc=lyude@redhat.com \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=phasta@kernel.org \
--cc=prafulrai522@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tamird@gmail.com \
--cc=tmgross@umich.edu \
--cc=viresh.kumar@linaro.org \
--cc=wedsonaf@gmail.com \
--cc=will@kernel.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