All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: xenomai@xenomai.org
Subject: [RFC] Rust API for evl
Date: Tue, 31 May 2022 15:37:35 +0200	[thread overview]
Message-ID: <87mtexkcxf.fsf@xenomai.org> (raw)


I've been getting my feet wet with Rust for a few weeks now, assessing
the real-time latency figures I could get from an existing (C++)
application once fully rewritten in this language.  It turned out that
performance was on par with the original implementation with memory
safety on top, among other upsides (like having quite some fun coding in
Rust in the first place).

Having Rust as a Tier 1 language for Xenomai4/evl along with the
existing C interface definitely makes sense to me. The goal would be to
have a 'revl' interface providing the EVL services the idiomatic Rust
way, available as a crate on top of the FFI bindings to libevl which
have just landed [1].

Whether you are a Rustacean or not, if you are willing to discuss and
help with this, let me know.

[1] https://source.denx.de/Xenomai/xenomai4/evl-sys.git

-- 
Philippe.


             reply	other threads:[~2022-05-31 13:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 13:37 Philippe Gerum [this message]
2022-06-01  5:50 ` [RFC] Rust API for evl Jan Kiszka
2022-06-01  8:56   ` Philippe Gerum
2022-06-05 14:49     ` Philippe Gerum

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=87mtexkcxf.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.