lkml.org 
[lkml]   [2016]   [Mar]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 7/9] NVMe: inform block layer of write cache state
    Date
    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
    \
     
     \ /
      Last update: 2016-03-30 17:21    [W:7.091 / U:0.036 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site