[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <8FA1F09F-CDD0-4A95-8E9E-49A3326613A2@collabora.com>
Date: Tue, 5 Aug 2025 09:41:43 -0300
From: Daniel Almeida <daniel.almeida@...labora.com>
To: Onur Özkan <work@...rozkan.dev>
Cc: Benno Lossin <lossin@...nel.org>,
Boqun Feng <boqun.feng@...il.com>,
linux-kernel@...r.kernel.org,
rust-for-linux@...r.kernel.org,
ojeda@...nel.org,
alex.gaynor@...il.com,
gary@...yguo.net,
a.hindborg@...nel.org,
aliceryhl@...gle.com,
tmgross@...ch.edu,
dakr@...nel.org,
peterz@...radead.org,
mingo@...hat.com,
will@...nel.org,
longman@...hat.com,
felipe_life@...e.com,
daniel@...lak.dev,
bjorn3_gh@...tonmail.com,
dri-devel <dri-devel@...ts.freedesktop.org>
Subject: Re: [PATCH v5 2/3] implement ww_mutex abstraction for the Rust tree
Hi Onur,
> On 5 Aug 2025, at 06:08, Onur Özkan <work@...rozkan.dev> wrote:
>
> On Sat, 2 Aug 2025 11:15:07 -0300
> Daniel Almeida <daniel.almeida@...labora.com> wrote:
>
>> Btw, I can also try to implement a proof of concept, so long as
>> people agree that this approach makes sense.
>
> It's not necessary to provide a full P.o.C but a small demonstration of
> the kind of ww_mutex API you would prefer would be helpful. Seeing a few
> sample Rust use-cases (especially in comparison to existing C
> implementations) would give a clearer picture for me.
>
> At the moment, the implementation is just a wrapper ([1]) around the C
> ww_mutex with no additional functionality, mostly because we don't have
> a solid consensus on the API design yet (we had some ideas about Tuple
> based approach, but seems like that isn't going to be useful for most
> of the ww_mutex users).
>
> [1]: https://github.com/onur-ozkan/linux/commits/673e01a9c309c
>
>> By the way, dri-devel seems to not be on cc? Added them now.
>
> Thanks!
>
> --
>
> Regards,
> Onur
>
This topic is on my TODO for this week.
— Daniel
Powered by blists - more mailing lists