Searched hist:248913 (Results 1 - 5 of 5) sorted by relevance
| /freebsd-11-stable/sys/dev/nvme/ | ||
| H A D | nvme_ctrlr_cmd.c | diff 248913 Fri Mar 29 18:37:17 MDT 2013 jimharris Add "type" to nvme_request, signifying if its payload is a VADDR, UIO, or NULL. This simplifies decisions around if/how requests are routed through busdma. It also paves the way for supporting unmapped bios. Sponsored by: Intel |
| H A D | nvme_ns_cmd.c | diff 248913 Fri Mar 29 18:37:17 MDT 2013 jimharris Add "type" to nvme_request, signifying if its payload is a VADDR, UIO, or NULL. This simplifies decisions around if/how requests are routed through busdma. It also paves the way for supporting unmapped bios. Sponsored by: Intel |
| H A D | nvme_qpair.c | diff 248913 Fri Mar 29 18:37:17 MDT 2013 jimharris Add "type" to nvme_request, signifying if its payload is a VADDR, UIO, or NULL. This simplifies decisions around if/how requests are routed through busdma. It also paves the way for supporting unmapped bios. Sponsored by: Intel |
| H A D | nvme_private.h | diff 248913 Fri Mar 29 18:37:17 MDT 2013 jimharris Add "type" to nvme_request, signifying if its payload is a VADDR, UIO, or NULL. This simplifies decisions around if/how requests are routed through busdma. It also paves the way for supporting unmapped bios. Sponsored by: Intel |
| H A D | nvme_ctrlr.c | diff 248913 Fri Mar 29 18:37:17 MDT 2013 jimharris Add "type" to nvme_request, signifying if its payload is a VADDR, UIO, or NULL. This simplifies decisions around if/how requests are routed through busdma. It also paves the way for supporting unmapped bios. Sponsored by: Intel |
Completed in 252 milliseconds