From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D815254BD7 for ; Mon, 8 Jan 2024 23:22:13 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="KDB0P/2F" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4B221C41674; Mon, 8 Jan 2024 23:22:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1704756133; bh=crA8XHgqOZT7OEkYYif3LCKS5ysNUNOhBQCamdokaLA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=KDB0P/2FSjGoOxnBeriBO5b91BLCW5G54tttt/Ft2V1NTDcTnTczGO2XTkQI7sBFt MPkxC0lofNORWX2b3BRe/oS5E7tWyBF4HYLcXTsomHMZDcICoTLrvOQLZ+DFgYDGDy uJL+GwdCa8mKTlgCDVUMqMco5cwCOBN3SBxQX1BwEBgotb17lcHyb6ye93OJ7JHFmQ 80zEhUmjDo4CHz/8P+7jZBiD0BT7MQnU1MZCZu6OcOA3OeS6R3gcsuJsGFY0xNV1+W g2BAnuaZ6gLy5mTUAg+Vi/O2PzWq6c6Yu+42XKJyKWDRftD1Pn+/TbcbcvhY/Fo13d /oEr+LzxVWYtw== Date: Mon, 8 Jan 2024 15:22:12 -0800 From: Saeed Mahameed To: Jakub Kicinski Cc: "Nelson, Shannon" , "David S. Miller" , Paolo Abeni , Eric Dumazet , Saeed Mahameed , netdev@vger.kernel.org, Tariq Toukan , Armen Ratner , Daniel Jurgens Subject: Re: [net-next 15/15] net/mlx5: Implement management PF Ethernet profile Message-ID: References: <20231221005721.186607-1-saeed@kernel.org> <20231221005721.186607-16-saeed@kernel.org> <20240104144446.1200b436@kernel.org> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20240104144446.1200b436@kernel.org> On 04 Jan 14:44, Jakub Kicinski wrote: >On Thu, 21 Dec 2023 14:25:33 -0800 Saeed Mahameed wrote: >> Maybe we should have made it clear here as well, this management PF just >> exposes a netdev on the embedded ARM that will be used to communicate >> with the device onboard BMC via NC-SI, so it meant to be used >> only by standard tools. > >How's that different to any other BMC via NC-SI setup? >NC-SI is supposed to steal packets which were directed to the wire. > This is embedded core switchdev setup, there is no PF representor, only uplink and VF/SF representors, the term management PF is only FW terminology, since uplink traffic is controlled by the admin, and uplink interface represents what goes in/out the wire, the current FW architecture demands that BMC/NCSI traffic goes through a separate PF that is not the uplink since the uplink rules are managed purely by the eswitch admin.