[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<174195723401.2241450.4794096109279890304.git-patchwork-notify@kernel.org>
Date: Fri, 14 Mar 2025 13:00:34 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Guangguan Wang <guangguan.wang@...ux.alibaba.com>
Cc: wenjia@...ux.ibm.com, pasic@...ux.ibm.com, jaka@...ux.ibm.com,
alibuda@...ux.alibaba.com, tonylu@...ux.alibaba.com, guwen@...ux.alibaba.com,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
horms@...nel.org, linux-rdma@...r.kernel.org, linux-s390@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v2] net/smc: use the correct ndev to find pnetid by
pnetid table
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@...emloft.net>:
On Tue, 4 Mar 2025 20:43:04 +0800 you wrote:
> When using smc_pnet in SMC, it will only search the pnetid in the
> base_ndev of the netdev hierarchy(both HW PNETID and User-defined
> sw pnetid). This may not work for some scenarios when using SMC in
> container on cloud environment.
> In container, there have choices of different container network,
> such as directly using host network, virtual network IPVLAN, veth,
> etc. Different choices of container network have different netdev
> hierarchy. Examples of netdev hierarchy show below. (eth0 and eth1
> in host below is the netdev directly related to the physical device).
> _______________________________
> | _________________ |
> | |POD | |
> | | | |
> | | eth0_________ | |
> | |____| |__| |
> | | | |
> | | | |
> | eth1|base_ndev| eth0_______ |
> | | | | RDMA ||
> | host |_________| |_______||
>
> [...]
Here is the summary with links:
- [net-next,v2] net/smc: use the correct ndev to find pnetid by pnetid table
https://git.kernel.org/netdev/net-next/c/bfc6c67ec2d6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists