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 68C6EC04FDE for ; Fri, 9 Dec 2022 09:30:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229810AbiLIJaC (ORCPT ); Fri, 9 Dec 2022 04:30:02 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49228 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229573AbiLIJaA (ORCPT ); Fri, 9 Dec 2022 04:30:00 -0500 Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F18D545EDA for ; Fri, 9 Dec 2022 01:29:56 -0800 (PST) Received: by mail-wr1-x42a.google.com with SMTP id u12so4569331wrr.11 for ; Fri, 09 Dec 2022 01:29:56 -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=Jd0Q9/mveJy0Lwn890efpGQgEXkOblEDmPcf79XrkkQ=; b=BT8fxi9GcEF2JyCMb8Sw0YghkV1c/k7p4wSo1ZRi8ISKDEv9M+srZUTiLhTqXRVNWZ KpVNa+wLoOioesFisqbxEas9MfFudH2Mk36PDRf/xYYIR4fsog7xadEN/de4gY+ZtSY7 GtTJrK0wYiJ9LiN/geBOGScUQmjWyAqzW3sF7HG0GdVxIX94Nx1huZ2oeIeugJzqaBQ7 I/Pn3+Pcs+6Gl9FwzbBIVpXMyn4mv6JrLCZ5cz+KGTHM4Rb35NiyFzwiLz1PZxtpVSAv 4CGADCOvupAvRj4aKWd0XciRT9y6YM4nJq1yOYi5vpKLit3Ob4LgWzQqJBZCkLEpRD7/ /otA== 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=Jd0Q9/mveJy0Lwn890efpGQgEXkOblEDmPcf79XrkkQ=; b=UZ4QWjNHqmM6J3MrU+fo8BqHq8t7SoiXIdCGJ45aesIxGve/fEQb2+wPL4QIxN4D+m VBBFI5vS1Zgg0G7Kk5TEgC4a3SZKUk19uh/0d34suasrjPIrhGeMP2tJ2K/8vAiYSmOg +Eorp9ygCpBK6XaOSmZuM9nhk+tnJ1OY19V+e64TCQAHrPQdfxIFF5gkwoosB1I2FqJy DOCpcH+08CENPEoxaBaogtWq7KDtaSWbqxhYNaMaVuO3f9ONissRs5gcvi1a0YGzcxuy JEuRriyLVhUoSPHYq4Bp2cLnh0f0Pl+ZWCf8ljsFYVm0nTKglN7mhFvxlUg4H5QN/e0j EqQA== X-Gm-Message-State: ANoB5pnppbFh489uk02kbxNY1G7ZScKzGrRTaN7cue3efbIBBzDso5QQ DjSSPfX3V/1Wf9ZTpuZZLlii+Q== X-Google-Smtp-Source: AA0mqf5OxOrmV8QTyiXLdwQu1aeyUmC111n5o9sLgwCXbheBLohpdtTgp/HYB9p5dVIz9VsnrJUCzw== X-Received: by 2002:adf:d202:0:b0:242:ac4:4a0c with SMTP id j2-20020adfd202000000b002420ac44a0cmr3966224wrh.32.1670578195531; Fri, 09 Dec 2022 01:29:55 -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 m6-20020a5d4a06000000b002420cfcd13dsm870752wrq.105.2022.12.09.01.29.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 09 Dec 2022 01:29:54 -0800 (PST) Date: Fri, 9 Dec 2022 10:29:53 +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: <20221205161933.663ea611@kernel.org> <20221206092705.108ded86@kernel.org> <20221207085941.3b56bc8c@kernel.org> <20221208081955.335ca36c@kernel.org> <20221208090517.643277e8@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221208090517.643277e8@kernel.org> Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Thu, Dec 08, 2022 at 06:05:17PM CET, kuba@kernel.org wrote: >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. Sure, so why it has to be netns aware if it has nothing to do with 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? I read this 5 times, I'm lost, don't understand what you mean :/ 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 14462C4332F for ; Fri, 9 Dec 2022 09:31:07 +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=LVYBOHNLlPsaeZc/JojMBQIB/2wMw3BEx4sZ4scBjTs=; b=xFJzfjL+CveSSK UP/jp5QmgFe3B2Ltkjjmq0UagzyTco82ryiJi66t8XfTTZrI5Jl6HpZ0UQ2pMW4u4slnwhvqeKvvb PtvAP28odTFM19mcjLyFq1pPP/Witrpc1rq9n9Ulx34T+KYxN6/s1HQKWOS6kiOlrR9vOS1BRH2gV qiU9Svz2zatJtJxHyHga2bUDAmeKqkRAlzY4MFFlgE2oDihP6mLP3JD771pl3mGaiyX9MstyDaZRu EExpreEjJIGvYSnbj5ktk/nLmQ4TpHg8dKYwLu1WWyjfpg+pyjfYjHh7SCUadauaLPbhipVfMMi4C bNAvsPOtCYHao/DmvUng==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1p3Zhi-006ByS-FS; Fri, 09 Dec 2022 09:30:02 +0000 Received: from mail-wr1-x42a.google.com ([2a00:1450:4864:20::42a]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1p3Zhe-006Bx2-E9 for linux-arm-kernel@lists.infradead.org; Fri, 09 Dec 2022 09:30:00 +0000 Received: by mail-wr1-x42a.google.com with SMTP id f18so4583738wrj.5 for ; Fri, 09 Dec 2022 01:29:56 -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=Jd0Q9/mveJy0Lwn890efpGQgEXkOblEDmPcf79XrkkQ=; b=BT8fxi9GcEF2JyCMb8Sw0YghkV1c/k7p4wSo1ZRi8ISKDEv9M+srZUTiLhTqXRVNWZ KpVNa+wLoOioesFisqbxEas9MfFudH2Mk36PDRf/xYYIR4fsog7xadEN/de4gY+ZtSY7 GtTJrK0wYiJ9LiN/geBOGScUQmjWyAqzW3sF7HG0GdVxIX94Nx1huZ2oeIeugJzqaBQ7 I/Pn3+Pcs+6Gl9FwzbBIVpXMyn4mv6JrLCZ5cz+KGTHM4Rb35NiyFzwiLz1PZxtpVSAv 4CGADCOvupAvRj4aKWd0XciRT9y6YM4nJq1yOYi5vpKLit3Ob4LgWzQqJBZCkLEpRD7/ /otA== 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=Jd0Q9/mveJy0Lwn890efpGQgEXkOblEDmPcf79XrkkQ=; b=FINs1CtSlMKhkkWrED6jKWuvc8nuz1eJOgsp8s2cGRh4vRMU5kyk6ucu4oAA+TCCWi FwAnFG88/J5o039FlZs+t78tZqlooNGeBZBeC0kDs8Lc/J+1G37URrtOhe6lag/6OBwv l/r3W9G7ghjLLhq+m677nXC1DW4iulubPVp1IFGLBLMZKf2azFfFSX0EuqpJlrEUbCBf 49Gxt3Lhj1Ehn5CNPzSmi3yyweqNoYWWGRShox5ZTXGAgt/bq8cQALYLK/mFLKE2veYE RfDwIBkU/QOYkyBUzdluGES0olbsakON7crbhRMQwIdVuEC36J7XoHNqfFYm+L11vE0+ P6xg== X-Gm-Message-State: ANoB5pmqmGWi+mtn6veLGgfPoelfYauniXaFf4/jI3ukgwe0+qctcVPS 00m+CkON3hLUlG7ak4vr15Z4fw== X-Google-Smtp-Source: AA0mqf5OxOrmV8QTyiXLdwQu1aeyUmC111n5o9sLgwCXbheBLohpdtTgp/HYB9p5dVIz9VsnrJUCzw== X-Received: by 2002:adf:d202:0:b0:242:ac4:4a0c with SMTP id j2-20020adfd202000000b002420ac44a0cmr3966224wrh.32.1670578195531; Fri, 09 Dec 2022 01:29:55 -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 m6-20020a5d4a06000000b002420cfcd13dsm870752wrq.105.2022.12.09.01.29.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 09 Dec 2022 01:29:54 -0800 (PST) Date: Fri, 9 Dec 2022 10:29:53 +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: <20221205161933.663ea611@kernel.org> <20221206092705.108ded86@kernel.org> <20221207085941.3b56bc8c@kernel.org> <20221208081955.335ca36c@kernel.org> <20221208090517.643277e8@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20221208090517.643277e8@kernel.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221209_012958_502489_52E6E057 X-CRM114-Status: GOOD ( 14.07 ) 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 Thu, Dec 08, 2022 at 06:05:17PM CET, kuba@kernel.org wrote: >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. Sure, so why it has to be netns aware if it has nothing to do with 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? I read this 5 times, I'm lost, don't understand what you mean :/ _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel