From: Waiman Long <longman@redhat.com>
To: Boqun Feng <boqun.feng@gmail.com>, Filipe Xavier <felipe_life@live.com>
Cc: aliceryhl@google.com, ojeda@kernel.org, gary@garyguo.net,
benno.lossin@proton.me, will@kernel.org,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v2] rust: add trylock method support for lock backend
Date: Tue, 24 Sep 2024 14:31:43 -0400 [thread overview]
Message-ID: <4c94912d-b0d9-4b7e-8490-ffd91fdd2184@redhat.com> (raw)
In-Reply-To: <ZvJkFr6kdVx8kIMq@boqun-archlinux>
On 9/24/24 03:02, Boqun Feng wrote:
>> +
>> +int rust_helper_spin_trylock(spinlock_t *lock)
>> +{
>> + return spin_trylock(lock);
>> +}
>> diff --git a/rust/kernel/sync/lock.rs b/rust/kernel/sync/lock.rs
>> index f6c34ca4d819..f4e51a5a1f23 100644
>> --- a/rust/kernel/sync/lock.rs
>> +++ b/rust/kernel/sync/lock.rs
>> @@ -58,6 +58,13 @@ unsafe fn init(
>> #[must_use]
>> unsafe fn lock(ptr: *mut Self::State) -> Self::GuardState;
>>
>> + /// Tries to acquire the lock without blocking.
> As I suggested in v1, "without blocking" is not accurate here because
> a lock can be a spinlock. So you can just remove it. I think the word
> "Tries" itself implies "neither busy waiting nor blocking".
Actually a spinlock in a PREEMPT_RT kernel is a sleeping lock. Not all
people will associate "Tries" with not blocking. Anyway, I don't think
it is a problem with the "without blocking" phrase.
Cheers,
Longman
next prev parent reply other threads:[~2024-09-24 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 15:23 [PATCH v2] rust: add trylock method support for lock backend Filipe Xavier
2024-09-24 7:02 ` Boqun Feng
2024-09-24 18:31 ` Waiman Long [this message]
2024-09-24 22:36 ` Boqun Feng
2024-09-25 1:27 ` Waiman Long
2024-09-24 20:24 ` Gary Guo
2024-09-24 23:33 ` Boqun Feng
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=4c94912d-b0d9-4b7e-8490-ffd91fdd2184@redhat.com \
--to=longman@redhat.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=boqun.feng@gmail.com \
--cc=felipe_life@live.com \
--cc=gary@garyguo.net \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--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