Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1363495
| Path | csiph.com!weretis.net!feeder4.news.weretis.net!news.mixmin.net!aioe.org!gothmog.csi.it!bofh.it!news.nic.it!robomod |
|---|---|
| From | Jens Axboe <axboe@fb.com> |
| Newsgroups | linux.kernel |
| Subject | [PATCH 7/8] NVMe: inform block layer of write cache state |
| Date | Wed, 23 Mar 2016 16:30:01 +0100 |
| Message-ID | <rfSTn-5lq-15@gated-at.bofh.it> (permalink) |
| References | <rfSTn-5lq-3@gated-at.bofh.it> |
| Dkim-Signature | v=1; a=rsa-sha256; c=relaxed/simple; d=fb.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type; s=facebook; bh=dF5FMExFNeu9xfS77NRZoMst7aWs+58X0AO//GYBVGg=; b=h32Gy4yS3K/3bSEeZKf55sY44zvW53zJIkznMljZ6oV5nrpn4ZxUxgBnpa+l5LBGvdsS Go7r2FxQ4MITPv0zkIWbpPaGaxNePODqg215m9djL9qn6RnUCY6HWrKJyruU5vIMufr1 8icGWBi5yBx9bjSpjmWeue8Urrib9OODw+g= |
| X-Mailer | git-send-email 2.4.1.168.g1ea28e1 |
| MIME-Version | 1.0 |
| Content-Type | text/plain |
| X-Originating-IP | [192.168.54.13] |
| X-Proofpoint-Spam-Reason | safe |
| X-Fb-Internal | Safe |
| X-Proofpoint-Virus-Version | vendor=fsecure engine=2.50.10432:,, definitions=2016-03-23_08:,, signatures=0 |
| Sender | robomod@news.nic.it |
| List-ID | <linux-kernel.vger.kernel.org> |
| X-Mailing-List | linux-kernel@vger.kernel.org |
| Approved | robomod@news.nic.it |
| Lines | 23 |
| Organization | linux.* mail to news gateway |
| X-Original-Cc | Jens Axboe <axboe@fb.com> |
| X-Original-Date | Wed, 23 Mar 2016 09:25:49 -0600 |
| X-Original-Message-ID | <1458746750-9213-8-git-send-email-axboe@fb.com> |
| X-Original-References | <1458746750-9213-1-git-send-email-axboe@fb.com> |
| X-Original-Sender | linux-kernel-owner@vger.kernel.org |
| Xref | csiph.com linux.kernel:1363495 |
Show key headers only | View raw
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.4.1.168.g1ea28e1
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
[PATCH 7/8] NVMe: inform block layer of write cache state Jens Axboe <axboe@fb.com> - 2016-03-23 16:30 +0100
csiph-web