From: Wedson Almeida Filho <wedsonaf@google.com>
To: Carlos <carloscarral13@gmail.com>
Cc: rust-for-linux@vger.kernel.org
Subject: Re: Exposing semaphores
Date: Tue, 27 Apr 2021 01:12:55 +0100 [thread overview]
Message-ID: <YIdXB88mPZ6alJix@google.com> (raw)
In-Reply-To: <YIdUf1C5VtWn/D2G@localhost.localdomain>
On Mon, Apr 26, 2021 at 07:02:07PM -0500, Carlos wrote:
> Semaphores are the first missing primitive that caught my attention, and
> being such an important part of the kernel itself, I will make exposing
> this functionality my first priority instead.
If the semaphores are used only for mutual exclusion, then you may want to just
use a mutex or spinlock that are already there. But that's only if you're
primarily interested in getting a rust scull to work first.
If you actually want to implement semaphores, go for it!
next prev parent reply other threads:[~2021-04-27 0:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 0:02 Exposing semaphores Carlos
2021-04-27 0:08 ` Alex Gaynor
2021-04-27 0:12 ` Wedson Almeida Filho [this message]
2021-04-27 1:43 ` Samantha Miller
2021-04-27 11:00 ` Sven Van Asbroeck
2021-04-27 10:18 ` Sven Van Asbroeck
2021-04-27 10:58 ` Greg KH
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=YIdXB88mPZ6alJix@google.com \
--to=wedsonaf@google.com \
--cc=carloscarral13@gmail.com \
--cc=rust-for-linux@vger.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;
as well as URLs for NNTP newsgroup(s).