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 54160C4332F for ; Wed, 2 Nov 2022 16:33:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231683AbiKBQdf (ORCPT ); Wed, 2 Nov 2022 12:33:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49834 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231673AbiKBQcc (ORCPT ); Wed, 2 Nov 2022 12:32:32 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 887F2193F5; Wed, 2 Nov 2022 09:28:49 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 2D7E8B823C2; Wed, 2 Nov 2022 16:28:48 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 62B85C433C1; Wed, 2 Nov 2022 16:28:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1667406526; bh=e2aDpYBoje0gQtLOnWkURg+egkBJ5OTswl+2K8lsdgQ=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=HiO4JfxxuAAPpmTP9FkhZY/y/ZPr6WR14zvPcvt9l5HxEIlqkef4h/il4382Af42F +Am4J1T7PMSRvsnHe9yAtW6tCF7ELP8cQ/hkJsUNRw8tpBKp0FCqtqBlPQ+fi81ypV ohIoSzGuenHncGbz/UaUUzIiyWsfLK318FeLgAzfIZ5ybp90IMUE3ab86P/srtvuEG 7VkuWNOXC7NXmQDX+PBZYowl/uSMop3ipMPVo4cgHWIAaWQQJ858r+yiZ5rmdwLNHD 3lc7iUja3NLF/YAi9LCwN1BU+WJUDExgVnFiqf3QnP+CX44l9jcMyzfOCpifkh0JFK HUYQ+kVnap2tA== Date: Wed, 2 Nov 2022 09:28:45 -0700 From: Jakub Kicinski To: Jiri Pirko Cc: netdev@vger.kernel.org, davem@davemloft.net, pabeni@redhat.com, edumazet@google.com, tariqt@nvidia.com, moshe@nvidia.com, saeedm@nvidia.com, linux-rdma@vger.kernel.org Subject: Re: [patch net-next v3 13/13] net: expose devlink port over rtnetlink Message-ID: <20221102092845.5e4f5ba0@kernel.org> In-Reply-To: References: <20221031124248.484405-1-jiri@resnulli.us> <20221031124248.484405-14-jiri@resnulli.us> <20221101091834.4dbdcbc1@kernel.org> <20221102081006.70a81e89@kernel.org> <20221102081325.2086edd8@kernel.org> <20221102085249.3b64e29f@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org On Wed, 2 Nov 2022 16:59:28 +0100 Jiri Pirko wrote: > Wed, Nov 02, 2022 at 04:52:49PM CET, kuba@kernel.org wrote: > >On Wed, 2 Nov 2022 16:37:00 +0100 Jiri Pirko wrote: > >> Or, even better, move RTnetlink to generic netlink. Really, there is no > >> point to have it as non-generic netlink forever. We moved ethtool there, > >> why not RTnetlink? > > > >As a rewrite? We could plug in the same callbacks into a genl family > >but the replies / notifications would have different headers depending > >on the socket type which gets hairy, no? > > I mean like ethtool, completely side iface, independent, new attrs etc. > We can start with NetdevNetlink for example. Just cover netdev part of > RTNetlink. That is probably most interesting anyway. That came up in conversations about the YAML specs. Major effort but may be worth doing.