linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Young <hidave.darkstar@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	linux-fsdevel@vger.kernel.org,
	Wu Fengguang <fengguang.wu@intel.com>
Subject: COW page cache for file hole?
Date: Wed, 4 May 2011 10:45:42 +0800	[thread overview]
Message-ID: <BANLkTiko7N=1w+Z56vuDcAUw5cHwgPi=1g@mail.gmail.com> (raw)

Hi,

During test fengguang's readahead alloc-noretry patch, I have some thoughts

In the 1000 dd case, page cache of sparse file hole are all zero indeed.
So what about make a global zero page for that purpose, fs level know
it is a hole,
when write occurs on that page we can alloc a new page for that.

I have no enough knowledge to implement it so just give out the
question without patch, sorry.
BTW, was there any attempt for this before?

-- 
Regards
dave

                 reply	other threads:[~2011-05-04  2:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='BANLkTiko7N=1w+Z56vuDcAUw5cHwgPi=1g@mail.gmail.com' \
    --to=hidave.darkstar@gmail.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).