mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>, Michal Hocko <mhocko@suse.com>,
	Mel Gorman <mgorman@suse.de>,
	Johannes Weiner <hannes@cmpxchg.org>, Tejun Heo <tj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH RFC] mm: implement write-behind policy for sequential file writes
Date: Mon, 2 Oct 2017 13:23:18 +0200	[thread overview]
Message-ID: <c684ee77-27a6-1522-b443-0c6d33d569a0@redhat.com> (raw)
In-Reply-To: <150693809463.587641.5712378065494786263.stgit@buzz>

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

  reply	other threads:[~2017-10-02 11:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-02  9:54 Konstantin Khlebnikov
2017-10-02 11:23 ` Florian Weimer [this message]
2017-10-02 11:55   ` Konstantin Khlebnikov
2017-10-02 19:54 ` Linus Torvalds
2017-10-02 20:58   ` Konstantin Khlebnikov
2017-10-02 22:29     ` Andreas Dilger
2017-10-02 22:45   ` Dave Chinner
2017-10-02 23:08     ` Linus Torvalds
2017-10-03  0:08       ` Dave Chinner
2017-10-02 20:00 ` Jens Axboe
2017-10-02 21:50   ` Konstantin Khlebnikov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c684ee77-27a6-1522-b443-0c6d33d569a0@redhat.com \
    --to=fweimer@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=hannes@cmpxchg.org \
    --cc=khlebnikov@yandex-team.ru \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@suse.com \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®