Message ID | 20191216190120.21374-1-logang@deltatee.com (mailing list archive) |
---|---|
Headers | show |
Series | Support hot-unbind in IOAT | expand |
On 16-12-19, 12:01, Logan Gunthorpe wrote: > Hey, > > This patchset creates some common infrastructure which I will use in the > next version of the PLX driver. It adds a reference count to the > dma_device struct which is taken and released every time a channel > is allocated or freed. A call back is used to allow the driver to > free the underlying memory and do any final cleanup. > > For a use-case, I've adjusted the ioat driver to properly support > hot-unbind. The driver was already pretty close as it already had > a shutdown state; so it mostly only required freeing the memory > correctly and calling ioat_shutdown at the correct time. I didnt find anything else (apart from one change i pointed), so I have applied this and will fix the comment. No point in delaying this
On 2019-12-23 9:50 p.m., Vinod Koul wrote: > On 16-12-19, 12:01, Logan Gunthorpe wrote: >> Hey, >> >> This patchset creates some common infrastructure which I will use in the >> next version of the PLX driver. It adds a reference count to the >> dma_device struct which is taken and released every time a channel >> is allocated or freed. A call back is used to allow the driver to >> free the underlying memory and do any final cleanup. >> >> For a use-case, I've adjusted the ioat driver to properly support >> hot-unbind. The driver was already pretty close as it already had >> a shutdown state; so it mostly only required freeing the memory >> correctly and calling ioat_shutdown at the correct time. > > I didnt find anything else (apart from one change i pointed), so I have > applied this and will fix the comment. No point in delaying this Great, thanks! Logan