[ofw] ctrl-c of appl

[Sean Hefty]

>Ok, I'm not sure if I agree that the problem I reported below with deregistermr
>not being called is the fault of the driver.

I believe that Tzachi was simply stating that the problem is with some kernel
driver.  I.e. it's not a library or user space application issue.

>When I get this bug check, it is because ibal has NOT called DeregisterMR; it
>only calls DestroyQp, DestroyCq and UmCloseCa.  How is the driver supposed to
>determine which MRs to automatically deregister?  An application could have
>created an MR for use with multiple QPs.  And, I don't think there is a way to
>connect an MR with a CA ctx.  Feel free to correct me if I'm wrong.

In this case, resource tracking is done with IBAL, so IBAL should be responsible
for tracking the memory registrations and deregistering the memory on
application failure.  Winverbs has a similar responsibility.

- Sean