> From: roland.dreier@xxxxxxxxx [mailto:roland.dreier@xxxxxxxxx] On Behalf > Of Roland Dreier > > Right, that's pretty much what I wrote. However I think it's a bit worse than "be > informed of this event and re-open the HCA context." > Userspace needs to synchronize with the kernel to wait for the uverbs device to > be torn down and recreated, and there's no guarantee that the device will come > back with the same name. (A perhaps contrived example is a glitch of a PCI > switch with multiple HCAs below it - we might reset and re-enumerate the HCAs > in a different order the second time around) > > - R. The "torn" part happens immediately. AFAIK, you won't be able to rebind to a failed device because it unregisters immediately. We are missing the plug-in event, but regarding device names an app can rely on the NodeGUID. Do you think that we need something more powerful to maintain the actual names, as done for netdevs (e.g., some udev rule that can modify the name assignment)? --Liran ��.n��������+%������w��{.n�����{���fk��ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
