> -----Original Message----- > From: longli@xxxxxxxxxxxxxxxxx <longli@xxxxxxxxxxxxxxxxx> > Sent: Tuesday, August 30, 2022 8:34 PM > To: KY Srinivasan <kys@xxxxxxxxxxxxx>; Haiyang Zhang > <haiyangz@xxxxxxxxxxxxx>; Stephen Hemminger > <sthemmin@xxxxxxxxxxxxx>; Wei Liu <wei.liu@xxxxxxxxxx>; Dexuan Cui > <decui@xxxxxxxxxxxxx>; David S. Miller <davem@xxxxxxxxxxxxx>; Jakub > Kicinski <kuba@xxxxxxxxxx>; Paolo Abeni <pabeni@xxxxxxxxxx>; Jason > Gunthorpe <jgg@xxxxxxxx>; Leon Romanovsky <leon@xxxxxxxxxx>; > edumazet@xxxxxxxxxx; shiraz.saleem@xxxxxxxxx; Ajay Sharma > <sharmaajay@xxxxxxxxxxxxx> > Cc: linux-hyperv@xxxxxxxxxxxxxxx; netdev@xxxxxxxxxxxxxxx; linux- > kernel@xxxxxxxxxxxxxxx; linux-rdma@xxxxxxxxxxxxxxx; Long Li > <longli@xxxxxxxxxxxxx> > Subject: [Patch v5 03/12] net: mana: Handle vport sharing between devices > > From: Long Li <longli@xxxxxxxxxxxxx> > > For outgoing packets, the PF requires the VF to configure the vport with > corresponding protection domain and doorbell ID for the kernel or user > context. The vport can't be shared between different contexts. > > Implement the logic to exclusively take over the vport by either the > Ethernet device or RDMA device. > > Reviewed-by: Dexuan Cui <decui@xxxxxxxxxxxxx> > Signed-off-by: Long Li <longli@xxxxxxxxxxxxx> Acked-by: Haiyang Zhang <haiyangz@xxxxxxxxxxxxx>
