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 9C39AC4332F for ; Thu, 8 Dec 2022 17:05:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230114AbiLHRFX (ORCPT ); Thu, 8 Dec 2022 12:05:23 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36226 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229745AbiLHRFW (ORCPT ); Thu, 8 Dec 2022 12:05:22 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 509CF2A711; Thu, 8 Dec 2022 09:05:21 -0800 (PST) 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 09C0DB82569; Thu, 8 Dec 2022 17:05:20 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 592BDC433D2; Thu, 8 Dec 2022 17:05:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1670519118; bh=mVa4rAGYCODwDCVnY1411oDOU/OwbCxVWI/1gCV76L4=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=TVJAMl42DI3KGjqjl4yeG1Wb6wkYJ+HxG3Pl28rRAwWLrbFkeKsbGjSrXw5wYJOQw Va7W/v57CD8QmKvGBsWThaTFS4pyk5a+1NVSc7aAtlFJ1E4OvTcIYHgCy7d7qmudi/ 3gQ8Shs0AxWEmrIMBtlkjow+1GOdhiFcCuburUbDwqgbyB8bVD1mPo28Enl7zPXLXS MsGC7E63EqRyb7lYqZ5kNjZ+lqeWMomsNqaP/kdEtnS1RjIbrYeTzQCUyrQEmqdvPW mFrc5X3u9GoSuA1hlt9zsMVWCOOJPKw41Jp6cn1W0EQdRbtH/YAkEFWNa1XKIxj6UH f6stCSkh8wQYA== Date: Thu, 8 Dec 2022 09:05:17 -0800 From: Jakub Kicinski To: Jiri Pirko Cc: "Kubalewski, Arkadiusz" , Vadim Fedorenko , Jonathan Lemon , Paolo Abeni , "netdev@vger.kernel.org" , Vadim Fedorenko , linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org, "Olech, Milena" , "Michalik, Michal" Subject: Re: [RFC PATCH v4 2/4] dpll: Add DPLL framework base functions Message-ID: <20221208090517.643277e8@kernel.org> In-Reply-To: References: <20221202212206.3619bd5f@kernel.org> <20221205161933.663ea611@kernel.org> <20221206092705.108ded86@kernel.org> <20221207085941.3b56bc8c@kernel.org> <20221208081955.335ca36c@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Thu, 8 Dec 2022 17:33:28 +0100 Jiri Pirko wrote: > For any synce pin manipulation over dpll netlink, we can use the netns > check of the linked netdev. This is the netns aware leg of the dpll, > it should be checked for. The OCP card is an atomic clock, it does not have any networking. > I can't imagine practically havind the whole dpll instance netns aware. > Omitting the fact that it really has no meaning for non-synce pins, what > would be the behaviour when for example pin 1 is in netns a, pin 2 in > netns b and dpll itself in netns c? To be clear I don't think it's a bad idea in general, I've done the same thing for my WIP PSP patches. But we already have one device without netdevs, hence I thought maybe devlink. So maybe we do the same thing with devlink? I mean - allow multiple devlink instances to be linked and require caps on any of them?