Sagi Grimberg 9b349b080c nvmet: Use direct IO for writes ... We're designed to work with high-end devices where direct IO makes perfect sense. We noticed that we context switch by scheduling kblockd instead of going directly to the device without REQ_SYNC for writes. Signed-off-by: Sagi Grimberg <sagi@grimberg.me> Reviewed-by: Jens Axboe <axboe@kernel.dk>		2016-09-23 15:37:38 -07:00
..
admin-cmd.c	admin-cmd: Added smart-log command support.	2016-09-23 15:37:37 -07:00
configfs.c	nvmet: fix an error code	2016-07-07 08:37:36 -06:00
core.c	nvmet: Fix controller serial number inconsistency	2016-08-04 17:45:10 +03:00
discovery.c
fabrics-cmd.c
io-cmd.c	nvmet: Use direct IO for writes	2016-09-23 15:37:38 -07:00
Kconfig	nvme-loop: fix nvme-loop Kconfig dependencies	2016-07-12 08:36:40 -07:00
loop.c	nvme-loop: Remove duplicate call to nvme_remove_namespaces	2016-08-03 16:25:19 +03:00
Makefile	nvmet-rdma: add a NVMe over Fabrics RDMA target driver	2016-07-08 08:38:49 -06:00
nvmet.h	nvmet: Fix controller serial number inconsistency	2016-08-04 17:45:10 +03:00
rdma.c	nvmet-rdma: Don't use the inline buffer in order to avoid allocation for small reads	2016-08-04 17:44:40 +03:00