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 CB1B622063 for ; Tue, 9 Jan 2024 02:58:08 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="YAw2IepC" Received: by smtp.kernel.org (Postfix) with ESMTPSA id E7462C433F1; Tue, 9 Jan 2024 02:58:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1704769088; bh=HDuOVydgFyWE9ffMato91sAIqwTUhAczbzijRUSkjuc=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=YAw2IepC5P27ANv5DHjFoAQVFPCqwAoARkZULz3cj8yoeYGvPc52l8VkICkBSk8gn 8ke+J8NJDFL8Qj4FG9RmtxkMIw3TTgHM+9OvLtGXyDulwfWvjxkKAH1lNaR+4SeLFf 5aoggvACoPZ5cOZbhA4bHFp9QLBNTbId3dNpJOHhFefn3Dfo5Fu/2kG6jzWSHx9WNF U2RliHfFuGpXqwEl2ygR/62AnYUyYG0wjTDQT+oM5LDKVQ2QrrnTMzsJRzWBXAKuDw xxybjsejitGltF5unx7Va5onQlipo+cU2tWX58AvN8Jx06Wyx9QMLShBffTxySQrJK vrciFWZARLvWQ== Date: Mon, 8 Jan 2024 18:58:06 -0800 From: Jakub Kicinski To: Saeed Mahameed 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: <20240108185806.6214cbe8@kernel.org> In-Reply-To: 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 Content-Transfer-Encoding: 7bit On Mon, 8 Jan 2024 15:22:12 -0800 Saeed Mahameed wrote: > 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. "Normal way" to talk to the BMC is to send the traffic to the uplink and let the NC-SI filter "steal" the frames. There's not need for host PF (which I think is what you're referring to when you say there's no PF representor). Can you rephrase / draw a diagram? Perhaps I'm missing something. When the host is managing the eswitch for mlx5 AFAIU NC-SI frame stealing works fine.. so I'm missing what's different with the EC.