From: Lorenzo Gabriele <[email protected]>
To: [email protected]
Subject: are volatile and memory barriers necessary for single threaded code?
Date: Mon, 4 May 2020 18:54:52 +0200 [thread overview]
Message-ID: <CAC40aqaSBwdBxQOn1T_ihtB=TnNLH91_xy05gFhvOG+3i3=ang@mail.gmail.com> (raw)
Hi everyone,
I'm a complete noob so sorry if I'm saying something stupid.
I want to have a liburing-like library for the Scala Native language.
I can't easily use liburing itself because of some limitations of the
language.. So I was rewriting the C code in liburing in Scala Native.
The language is single threaded and, sadly, doesn't support atomic,
nor volatile. I was thinking what are the implications of completely
removing the memory barriers.
Are they needed for something related with multithreading or they are
needed regardless to utilize io_uring?
Thank you very much.
Lorenzo
next reply other threads:[~2020-05-04 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 16:54 Lorenzo Gabriele [this message]
2020-05-06 13:44 ` are volatile and memory barriers necessary for single threaded code? Pavel Begunkov
2020-05-18 11:31 ` Lorenzo Gabriele
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='CAC40aqaSBwdBxQOn1T_ihtB=TnNLH91_xy05gFhvOG+3i3=ang@mail.gmail.com' \
[email protected] \
[email protected] \
/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