From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 604F8C3064E for ; Thu, 17 Aug 2023 15:15:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1353020AbjHQPPZ (ORCPT ); Thu, 17 Aug 2023 11:15:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33854 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1353030AbjHQPOs (ORCPT ); Thu, 17 Aug 2023 11:14:48 -0400 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1A93D2D74; Thu, 17 Aug 2023 08:14:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=+IFPX83lPaAOGdnhnP/eIMxERGqSGxvY5B0ikm9lkO0=; b=2w9misJitUSHvle93U8BZqSrbP 9clMJJvZImdBdayMGB06Nhk5YYHLNh37NSV8kJxI5/4m4bdJEEDvYGgswEAmDo+CxBGxM1ikKG4nk kL5u4nSoEpzoMAqI9xLLAz6F/UV4oG0eCDuUPfMdG8vQ9Tn7YTMrP2AxYunh1sTV9QIk=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1qWehb-004OhF-LW; Thu, 17 Aug 2023 17:14:23 +0200 Date: Thu, 17 Aug 2023 17:14:23 +0200 From: Andrew Lunn To: Michele Dalle Rive Cc: Greg KH , Miguel Ojeda , Alex Gaynor , Wedson Almeida Filho , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Boqun Feng , Gary Guo , =?iso-8859-1?Q?Bj=F6rn?= Roy Baron , Benno Lossin , Alice Ryhl , Davide Rovelli , rust-for-linux@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, patches@lists.linux.dev Subject: Re: [RFC PATCH 0/7] Rust Socket abstractions Message-ID: <9cb6cb27-bcde-46a1-a7ec-fb251c64fb67@lunn.ch> References: <20230814092302.1903203-1-dallerivemichele@gmail.com> <2023081411-apache-tubeless-7bb3@gregkh> <0e91e3be-abbb-4bf7-be05-ba75c7522736@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > I am wondering whether the `net` subsystem is interested in reviewing, giving > feedback and eventually accepting code that is currently OOT-only. netdev, and the linux kernel in general, has no interest in code to support out of tree modules. It adds maintenance cost for no gain. > Also, it would be interesting if you could provide us any module or > functionality you are planning to get in-tree which might use this interface; > it could be useful in order to understand the applicability of these > abstractions and find a concrete in-kernel use-case. You need real code which does something useful for the community. Your problem is, there is little use of sockets inside the kernel. I did list a few examples in my first reply. Network file systems, logging kernel messages to a remote server. I thought of one more afterwards, there is dhcp client code used for NFS root, which could make use of raw sockets. However, you have the problem you cannot just rewrite this existing code in Rust because it is core code and needs to work on all architectures. And my understanding is, there are currently not Rust compilers for all architectures. What you can however do is implement something new, which the kernel does not have. If it never existed, it is hard to complain it is only available for a restricted number of architectures. So maybe look through the RFCs and IETF documents and see if you can find something which is both useful, and makes sense to be implemented in the kernel. Andrew