aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/nvme
diff options
context:
space:
mode:
authorSagi Grimberg <sagi@grimberg.me>2016-09-21 11:06:32 -0700
committerSagi Grimberg <sagi@grimberg.me>2016-09-23 15:37:38 -0700
commit9b349b080ca9777f6dab3da06d7fa4577f7d4c29 (patch)
tree0071a47de72b0f5d23b83a5008830eac4bba92e5 /drivers/nvme
parentadmin-cmd: Added smart-log command support. (diff)
downloadlinux-dev-9b349b080ca9777f6dab3da06d7fa4577f7d4c29.tar.xz
linux-dev-9b349b080ca9777f6dab3da06d7fa4577f7d4c29.zip
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>
Diffstat (limited to 'drivers/nvme')
-rw-r--r--drivers/nvme/target/io-cmd.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/nvme/target/io-cmd.c b/drivers/nvme/target/io-cmd.c
index 2cd069b691ae..4132b6b98182 100644
--- a/drivers/nvme/target/io-cmd.c
+++ b/drivers/nvme/target/io-cmd.c
@@ -58,6 +58,7 @@ static void nvmet_execute_rw(struct nvmet_req *req)
if (req->cmd->rw.opcode == nvme_cmd_write) {
op = REQ_OP_WRITE;
+ op_flags = WRITE_ODIRECT;
if (req->cmd->rw.control & cpu_to_le16(NVME_RW_FUA))
op_flags |= REQ_FUA;
} else {