Searched hist:297858 (Results 1 - 4 of 4) sorted by relevance
| /freebsd-11-stable/sys/dev/isp/ | ||
| H A D | isp_freebsd.h | diff 297858 Tue Apr 12 12:30:48 MDT 2016 mav Allocate separate DMA area for synchronous IOCB execution. Usually IOCBs should be put on queue for asynchronous processing and should not require additional DMA memory. But there are some cases like aborts and resets that for external reasons has to be synchronous. Give those cases separate 2*64 byte DMA area to decouple them from other DMA scratch area users, using it for asynchronous requests. |
| H A D | ispvar.h | diff 297858 Tue Apr 12 12:30:48 MDT 2016 mav Allocate separate DMA area for synchronous IOCB execution. Usually IOCBs should be put on queue for asynchronous processing and should not require additional DMA memory. But there are some cases like aborts and resets that for external reasons has to be synchronous. Give those cases separate 2*64 byte DMA area to decouple them from other DMA scratch area users, using it for asynchronous requests. |
| H A D | isp_pci.c | diff 297858 Tue Apr 12 12:30:48 MDT 2016 mav Allocate separate DMA area for synchronous IOCB execution. Usually IOCBs should be put on queue for asynchronous processing and should not require additional DMA memory. But there are some cases like aborts and resets that for external reasons has to be synchronous. Give those cases separate 2*64 byte DMA area to decouple them from other DMA scratch area users, using it for asynchronous requests. |
| H A D | isp.c | diff 297858 Tue Apr 12 12:30:48 MDT 2016 mav Allocate separate DMA area for synchronous IOCB execution. Usually IOCBs should be put on queue for asynchronous processing and should not require additional DMA memory. But there are some cases like aborts and resets that for external reasons has to be synchronous. Give those cases separate 2*64 byte DMA area to decouple them from other DMA scratch area users, using it for asynchronous requests. |
Completed in 305 milliseconds