Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1367276
| From | Jens Axboe <axboe@fb.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | [PATCH 7/9] NVMe: inform block layer of write cache state |
| Date | 2016-03-30 17:10 +0200 |
| Message-ID | <ripUS-7fj-23@gated-at.bofh.it> (permalink) |
| References | <ripUS-7fj-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
This isn't quite correct, since the VWC merely states if a potential write back cache is volatile or not. But for the purpose of write absortion, it's good enough. Signed-off-by: Jens Axboe <axboe@fb.com> --- drivers/nvme/host/core.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c index 643f457131c2..05c8edfb7611 100644 --- a/drivers/nvme/host/core.c +++ b/drivers/nvme/host/core.c @@ -906,6 +906,7 @@ static void nvme_set_queue_limits(struct nvme_ctrl *ctrl, if (ctrl->vwc & NVME_CTRL_VWC_PRESENT) blk_queue_flush(q, REQ_FLUSH | REQ_FUA); blk_queue_virt_boundary(q, ctrl->page_size - 1); + blk_queue_write_cache(q, ctrl->vwc & NVME_CTRL_VWC_PRESENT); } /* -- 2.8.0.rc4.6.g7e4ba36
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
[PATCH 7/9] NVMe: inform block layer of write cache state Jens Axboe <axboe@fb.com> - 2016-03-30 17:10 +0200
csiph-web