Netdev List
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Lane <software.research.development@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [net] Search for net subsystem rust abstractions in-progress
Date: Fri, 25 Sep 2026 22:03:41 +0200	[thread overview]
Message-ID: <ff9b5057-c720-4e5b-b1b9-6c797c856ff7@lunn.ch> (raw)
In-Reply-To: <CAGchGNseHg7k=Ubtmck=Tc0U3z=wJefEE5kKdH1wxOH5wXS4PA@mail.gmail.com>

On Thu, Sep 24, 2026 at 09:48:13PM -0500, Lane wrote:
> Hi,
> 
> I am following up on some advice given from the Rust forums where I am
> trying to move some of my LKM's from C to Rust. These LKM's,basically
> create new address family protocols using (for starters) structs and
> functions like the following:
> 
>     struct net_proto_family;
>     struct proto_ops;
> 
>     // Add a socket protocol handler
>     err = sock_register(&proto_family);
> 
> These do not appear in the kernel crate. Per the
> submitting-new-abstractions-and-modules section for contributions in
> rust-for-linux, the second bullet point says to "check the mailing
> list archive" because "part of the work may be already done or in the
> process of being upstreamed", so I was hoping to see where things
> stand and get advice.

There have not been any contributions on adding new address families
from rust.

It is also somewhat unusual to add new address families. So before you
go too far, you might want to give a high level description of what
you are doing, just to make sure your architecture is correct.

	Andrew

  reply	other threads:[~2026-09-25 20:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25  2:48 [net] Search for net subsystem rust abstractions in-progress Lane
2026-09-25 20:03 ` Andrew Lunn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-09-26  3:26 Lane

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=ff9b5057-c720-4e5b-b1b9-6c797c856ff7@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=netdev@vger.kernel.org \
    --cc=software.research.development@gmail.com \
    /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