linux-kernel - Re: [PATCH 1/2] rust: add Soft-RoCE driver basic structure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 30 Sep 2023 20:22:14 +0200
From:   Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To:     AllenX <xubo3006@....com>
Cc:     rust-for-linux@...r.kernel.org, ojeda@...nel.org,
        alex.gaynor@...il.com, wedsonaf@...il.com, boqun.feng@...il.com,
        gary@...yguo.net, bjorn3_gh@...tonmail.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] rust: add Soft-RoCE driver basic structure

On Sat, Sep 30, 2023 at 6:16 PM AllenX <xubo3006@....com> wrote:
>
> add soft-Roce rxe device net driver basic structure and Rust security abstration interface
>
> This patch add Rust abstration for rdma Soft-RoCE drrivers.
> The basic architecture is completed, initialization is implemented and interfaces are set aside. Network driver-related support is currently not perfect, and the specific functions of data frame parsing need to be further implemented.
> [PATCH 2/2] is the driver of rdma infiniband mlx4 and also completes a similar basic architecture.

Thanks for the patches! It is nice to see people interested in Rust
for more use cases.

On top of what Trevor said, please see:

    https://rust-for-linux.com/contributing

There is some extra information there that is important, such as
Cc'ing the relevant C side maintainers and lists, since they are the
ones that will have to agree to take these abstractions. In this case,
I would imagine that would be, at least, the InfiniBand maintainers
and the rdma list.

Moreover, please note that these patches seem to be on top of the
`rust` branch. Patches sent to the mailing list should generally be
based on top of one of the latest Linus' tags or `rust-next`. If your
abstractions require dependencies that have not arrived yet into
mainline, those will need to be upstreamed too. Please see the website
above for more details on this, e.g.

    https://rust-for-linux.com/branches

Cheers,
Miguel