All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Guilherme Novaes Lima <acc.guilhermenl@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Seeking guidance on Rust porting for network driver as a learning project
Date: Fri, 15 Aug 2025 10:11:55 -0700	[thread overview]
Message-ID: <20250815101155.0c777734@kernel.org> (raw)
In-Reply-To: <355E9163-9274-49C3-98AB-7354B9C091B7@gmail.com>

On Fri, 15 Aug 2025 12:05:14 -0300 Guilherme Novaes Lima wrote:
> I’m a computer science student working on a graduation project
> focused on learning more about the Linux kernel and Rust. I
> understand that the kernel maintainers have been cautious about
> integrating Rust, and my intention is not to push for any immediate
> changes, but rather to explore Rust porting as a learning exercise.
> 
> Specifically, I’m interested in working with a network driver to get
> hands-on experience. My goal is to comply fully with the community’s
> expectations and guidelines, and to better understand the technical
> and cultural aspects before considering any real contributions in the
> future.
> 
> If there are any maintainers or experienced folks willing to offer
> guidance or suggest a suitable driver for this kind of project, I’d
> be very grateful. I’m not asking anyone to do the work, just hoping
> to learn and engage respectfully with the community.

You are specifically asking about in-kernel network driver code,
which, well, perhaps this is too blunt but personally feels like
a significant waste of community/reviewer time.

If you're open to kernel-related but user space coding - a port of YNL
to Rust would be most useful:
https://docs.kernel.org/next/userspace-api/netlink/intro-specs.html#ynl-lib
We have sort-of-a-port from C to C++ here:
https://github.com/linux-netdev/ynl-cpp
But nobody to my knowledge attempted a Rust version.

  reply	other threads:[~2025-08-15 17:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15 15:05 Seeking guidance on Rust porting for network driver as a learning project Guilherme Novaes Lima
2025-08-15 17:11 ` Jakub Kicinski [this message]
2025-08-15 19:10 ` Andrew Lunn
2025-08-15 19:23   ` Andrew Lunn
  -- strict thread matches above, loose matches on Subject: below --
2025-08-15 23:27 Guilherme Novaes Lima
2025-08-16  0:30 ` Andrew Lunn
2025-08-15 14:27 Guilherme Novaes Lima

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=20250815101155.0c777734@kernel.org \
    --to=kuba@kernel.org \
    --cc=acc.guilhermenl@gmail.com \
    --cc=netdev@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.