-----"Jason Gunthorpe" <jgg@xxxxxxxx> wrote: ----- >To: "Bernard Metzler" <BMT@xxxxxxxxxxxxxx> >From: "Jason Gunthorpe" <jgg@xxxxxxxx> >Date: 02/12/2019 07:13PM >Cc: linux-rdma@xxxxxxxxxxxxxxx >Subject: Re: [PATCH v4 03/13] SIW network and RDMA core interface > >On Tue, Feb 12, 2019 at 05:03:30PM +0000, Bernard Metzler wrote: > >> >If you want to expedite removal of uverbs then siw has to support >the >> >uverbs 'disassociate' flow. >> > >> Ah OK. I was not aware of that. Do we have an example provider >> code for that to help me understanding that flow? I just see a few >> providers with empty disassociate_ucontext functions. I am not sure >> this is what it should be? > >It is supposed to be empty, this is something that needs to be >cleaned >up. > Okay. Maybe my comments were misleading. I didn't want to kill the application, but maintain internal QP state appropriate. If I know the port is going down, I shall mark the affected SQ's appropriately. siw is a dumb sw implementation of real hardware - which of course also would maintain its internal QP's state accordingly... Best, Bernard.
