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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 846B4C3A5A7 for ; Thu, 8 Dec 2022 08:16:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=6Jt5hq7CepLKHHeAWn6lSJJqu7Q1L7UHP+ZwWb/5MMM=; b=NYoE9WAY4hgMpx hiRiUkYwI25QQI8OCizD9KIAJdHfrgObwmCc+XTDKhwnYNMBhLVWVGfRVD3A+CJUEpfn4YssOVoaR 6nP48MZwgq+Xo+NWGK6V77ESOYOA9r8vBTpSQ/MWlsJ+aPX9ayBXGTqi+K8WcH2ggeXKcJMNIfqrZ UzPKQ0GWmAiI7KnYV3dE2BC0b9B+S6g3e9WH4NUX+WIz2+ipBggD7hCFv9bwki2lU8ondd/qQ+EO1 y2wLLIX7d2kw71zQK+TlGUf10DeysPndGAnELgSLqNfE4wH6JMrblkpvZ6+e4OaPiWU3zJKBnHxTG IJq2UH0el5is1pyr4lFQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1p3C3H-009Juf-Mw; Thu, 08 Dec 2022 08:14:43 +0000 Received: from mail-ej1-x636.google.com ([2a00:1450:4864:20::636]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1p3C3C-009JPU-4I for linux-arm-kernel@lists.infradead.org; Thu, 08 Dec 2022 08:14:40 +0000 Received: by mail-ej1-x636.google.com with SMTP id qk9so2088419ejc.3 for ; Thu, 08 Dec 2022 00:14:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=resnulli-us.20210112.gappssmtp.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=wtVgzA0tnlZYI2aQPk1Vlp2tJRyR1xpHtf5sM5xwTWQ=; b=sZH1isJgfoNIVB/FF0/v8QvXTxuSipN5HfMpapXocHA4KJCeVgRNKwPjqr/TFZxV1q thDN8K+mRT1qgCTnHHxytTPolDk0fksikTbmmfVet5MhYVG3gAzcVmEiYS2AeAjJNQ2T D9z3ngNer4R9QgqcKWHe8bMSdePgoD7STyE+Om3va0IdEGAfk95DtDWlDN6yH97WywXL wyGuTsa/5FH7nlYlyRHdteo2crpGhXtMV+pdlzhsNr7V9y6APtXvb+ajU0Gd8BOez/z9 zszhdaVhLCopWCyLZEpEm47xS/L+DoNaIpkbhIFaaeb/yj+hEdHxDzbhlK/NRE2wJijM Zskw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=wtVgzA0tnlZYI2aQPk1Vlp2tJRyR1xpHtf5sM5xwTWQ=; b=71u8G5IO6fIQeQbr+BXkuFib+eRGAWpQ8AjkrPge8NM5+IW7LvBnMCoXpDFOgUYO6M aCuk/tQKiHTlA5YNdnIVyn8jI4T+3OfSmu18/F2YR1L/1VeNNlK16sqJr8NRvHsZ9WFV cGUTORj0eACtc70WqgyTruN8LXaUTN/TMy+I8qsBhiBjJ8MWHC7n++FOyyZmS2Dd5v1B 3+npcNptq1tVNnqcWLNPLx5P/ZNx4WRG6V859XnXP0stMXrg+Yqll4jHXOwxFXVHhut2 5AkYIWFMRjej5/31WRNEZpFlskv5eAxCavsq74EBvKWoOihS6lzpo9PZc+Yq2ccUt8fz ruwg== X-Gm-Message-State: ANoB5pkoAym9gqlpPfJB0nRLZqslY4YOTFVizbYQ2U4AAxLetx2drciq tkw/SW52VpoITixaend6CQ1P1w== X-Google-Smtp-Source: AA0mqf4NyhJRCYAiiDE9inktT3l2ge/UojNytsLFHAEpTHJi27kRn68d/faKrdITHVOl8NL+90ZPgg== X-Received: by 2002:a17:907:d412:b0:7c0:8e62:56f6 with SMTP id vi18-20020a170907d41200b007c08e6256f6mr1586320ejc.56.1670487273940; Thu, 08 Dec 2022 00:14:33 -0800 (PST) Received: from localhost (host-213-179-129-39.customer.m-online.net. [213.179.129.39]) by smtp.gmail.com with ESMTPSA id r10-20020a17090609ca00b007ad94422cf6sm9296799eje.198.2022.12.08.00.14.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 08 Dec 2022 00:14:33 -0800 (PST) Date: Thu, 8 Dec 2022 09:14:32 +0100 From: Jiri Pirko To: Jakub Kicinski 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: References: <20221202212206.3619bd5f@kernel.org> <20221205161933.663ea611@kernel.org> <20221206092705.108ded86@kernel.org> <20221207085941.3b56bc8c@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20221207085941.3b56bc8c@kernel.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221208_001438_426491_E6E66B30 X-CRM114-Status: GOOD ( 15.60 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Wed, Dec 07, 2022 at 05:59:41PM CET, kuba@kernel.org wrote: >On Wed, 7 Dec 2022 14:10:42 +0100 Jiri Pirko wrote: >> >> Why do we need this association at all? >> > >> >Someone someday may want netns delegation and if we don't have the >> >support from the start we may break backward compat introducing it. >> >> Hmm. Can you imagine a usecase? > >Running DPLL control in a namespace / container. > >I mean - I generally think netns is overused, but yes, it's what >containers use, so I think someone may want to develop their >timer controller SW in as a container? The netdevices to control are already in the container. Isn't that enough? > >> Link to devlink instance btw might be a problem. In case of mlx5, one >> dpll instance is going to be created for 2 (or more) PFs. 1 per ConnectX >> ASIC as there is only 1 clock there. And PF devlinks can come and go, >> does not make sense to link it to any of them. > >If only we stuck to the "one devlink instance per ASIC", huh? :) Yeah... > >> Thinking about it a bit more, DPLL itself has no network notion. The >> special case is SyncE pin, which is linked to netdevice. Just a small >> part of dpll device. And the netdevice already has notion of netns. >> Isn't that enough? > >So we can't use devlink or netdev. Hm. So what do we do? >Make DPLLs only visible in init_net? And require init_net admin? >And when someone comes asking we add an explicit "move to netns" >command to DPLL? Well, as I wrote. The only part needed to be network namespaced are the netdev related pins. And netdevices have netns support. So my question again, why is that not enough? _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel