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 X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2DDDBC3F2D7 for ; Thu, 5 Mar 2020 15:01:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0067F208CD for ; Thu, 5 Mar 2020 15:01:19 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="g5rhbu4N" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726917AbgCEPBS (ORCPT ); Thu, 5 Mar 2020 10:01:18 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:50821 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726178AbgCEPBS (ORCPT ); Thu, 5 Mar 2020 10:01:18 -0500 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id DA8AC2241C; Thu, 5 Mar 2020 10:01:16 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Thu, 05 Mar 2020 10:01:16 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=+DeXsw il40YIVs1J0/sih2u3eHdfb9FN+gx7TY4Aqzs=; b=g5rhbu4NYzRgkBKXiUm9jc HjSUz1IJVrtHXo310LfJsM27A9295V6a32TVfust7uqueePGLlh8dwl/K+xCmEnO 2sa8xtJ1rhAfLXXRoLzyHfhfCeaLjGIQvPywYwvDoDrG9MlmhLWc9ocdOy/haqbV aREQFhZQhotKzU/LjHWnfZZTdCNVJjIUXVA3Tf/EzIdWveBuFY74q9RmkDCvp1at 5xj3NVIaDj9dFqtiCa7J0neKVeyFjYJYRPJSBRBmQIaJJ98Ko7r+Rc0K0JsDZrqv yoHY08VJXuv7tbdvYRe60yP9j1p4hitQPrEo+mkArvCwIwHjWmirmO9Nkxu5qXqQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedruddutddgjeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpefkughoucfu tghhihhmmhgvlhcuoehiughoshgthhesihguohhstghhrdhorhhgqeenucfkphepudelfe drgeejrdduieehrddvhedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehm rghilhhfrhhomhepihguohhstghhsehiughoshgthhdrohhrgh X-ME-Proxy: Received: from localhost (unknown [193.47.165.251]) by mail.messagingengine.com (Postfix) with ESMTPA id A840D3280064; Thu, 5 Mar 2020 10:01:15 -0500 (EST) Date: Thu, 5 Mar 2020 17:01:14 +0200 From: Ido Schimmel To: Vadym Kochan Cc: "linux-kernel@vger.kernel.org" , "netdev@vger.kernel.org" , "David S . Miller" , Oleksandr Mazur , Taras Chornyi , Serhiy Boiko , Andrii Savka , Volodymyr Mytnyk Subject: Re: [RFC net-next 0/3] net: marvell: prestera: Add Switchdev driver for Prestera family ASIC device 98DX326x (AC3x) Message-ID: <20200305150114.GB132852@splinter> References: <20200225163025.9430-1-vadym.kochan@plvision.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200225163025.9430-1-vadym.kochan@plvision.eu> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 25, 2020 at 04:30:52PM +0000, Vadym Kochan wrote: > Marvell Prestera 98DX326x integrates up to 24 ports of 1GbE with 8 > ports of 10GbE uplinks or 2 ports of 40Gbps stacking for a largely > wireless SMB deployment. It seems that this device has enough ports to loopback to each other in order to create meaningful topologies. Therefore, I suggest running relevant existing tests under tools/testing/selftests/net/forwarding/ and contributing new ones. See tools/testing/selftests/net/forwarding/README for details. One problem you will run into is that your netdev notifier only allows bridge uppers and will therefore veto VRF uppers, which is a prerequisite. However, since you don't support L3 offload, then all routed traffic should reach the CPU anyway and therefore VRF uppers can be allowed.