Michael S. Tsirkin wrote:
An additional thinking behind this is: ULPs (e.g. SDP, CM)
need to keep lists of per-device objects and kill them on device
removal.
For example with change Sean proposes SDP will need to keep
a list of per-device cm_ids in each connection.
One idea, then, is in this example to make each cm_id a client,
then this list is managed by device.c
Client list then becomes very long, so its important to get
client data from device without scanning the client list.
How does SDP currently track QPs? You should be able to track most cm_id's
using the same method. Only listen cm_id's should need to be tracked separately.
If we're trying to solve the issue of searching a list looking for user context
after a remove event occurs, can't we just modify the remove device handling and
pass in the user context? Is this the extent of your proposal, or am I missing
something else?
- Sean
_______________________________________________
openib-general mailing list
[email protected]
http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
