From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751166AbdJBLXZ (ORCPT ); Mon, 2 Oct 2017 07:23:25 -0400 Received: from mx1.redhat.com ([209.132.183.28]:34298 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750929AbdJBLXX (ORCPT ); Mon, 2 Oct 2017 07:23:23 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 24E79806A3 Authentication-Results: ext-mx02.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx02.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=fweimer@redhat.com Subject: Re: [PATCH RFC] mm: implement write-behind policy for sequential file writes To: Konstantin Khlebnikov , linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Cc: Jens Axboe , Michal Hocko , Mel Gorman , Johannes Weiner , Tejun Heo , Andrew Morton , Linus Torvalds References: <150693809463.587641.5712378065494786263.stgit@buzz> From: Florian Weimer Message-ID: Date: Mon, 2 Oct 2017 13:23:18 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <150693809463.587641.5712378065494786263.stgit@buzz> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Mon, 02 Oct 2017 11:23:23 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/02/2017 11:54 AM, Konstantin Khlebnikov wrote: > This patch implements write-behind policy which tracks sequential writes > and starts background writeback when have enough dirty pages in a row. Does this apply to data for files which have never been written to disk before? I think one of the largest benefits of the extensive write-back caching in Linux is that the cache is discarded if the file is deleted before it is ever written to disk. (But maybe I'm wrong about this.) Thanks, Florian