All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Howard Lau <howardlau1999@hotmail.com>
Cc: rust-for-linux <rust-for-linux@vger.kernel.org>
Subject: Re: Does Rust for Linux support kernel socket programming now?
Date: Mon, 11 Apr 2022 11:08:52 +0200	[thread overview]
Message-ID: <CANiq72=4yuGunw_cQSNqrhRtHbE2CWy04WDGs4iA=ceC34QMQA@mail.gmail.com> (raw)
In-Reply-To: <OSZP286MB21285514FAC4E0FFBAEA6CA0B8E89@OSZP286MB2128.JPNP286.PROD.OUTLOOK.COM>

Hi Howard,

On Mon, Apr 11, 2022 at 2:18 AM Howard Lau <howardlau1999@hotmail.com> wrote:
>
> Hi, I am quite interested in developing safe kernel modules with Rust for Linux, but it seems that the project hasn't added support for kernel mode socket programming yet (as I didn't find anything related to socket except for `SkBuff` in `kernel::net`).
> I am working on a high-performance network file system and looking for a way to use API such as `sock_create_kern` and send and receive network messages in the kernel with Rust for Linux. Could anyone please tell me if I am missing something or there is a workaround for this?

For missing kernel APIs, safe abstractions should be added and then
used from the module. If you want to experiment, then a workaround is
calling the C functions directly through the bindings for the moment.

> Thanks!
> P.S. I would also like to join the zulip group. My email address is howardlau1999@hotmail.com.

Invitation sent, welcome!

Cheers,
Miguel

  reply	other threads:[~2022-04-11  9:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-09 15:58 Does Rust for Linux support kernel socket programming now? Howard Lau
2022-04-11  9:08 ` Miguel Ojeda [this message]
2022-04-09 16:12 Howard Lau
2022-04-11 12:57 ` Miguel Ojeda

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='CANiq72=4yuGunw_cQSNqrhRtHbE2CWy04WDGs4iA=ceC34QMQA@mail.gmail.com' \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=howardlau1999@hotmail.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 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.