From: Christoph Lameter <clameter@engr.sgi.com>
To: Ingo Oeser <ioe-lkml@rameria.de>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Badari Pulavarty <pbadari@us.ibm.com>,
andrea@suse.de, hugh@veritas.com, linux-mm@kvack.org
Subject: Re: [RFC] sys_punchhole()
Date: Fri, 11 Nov 2005 11:07:34 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.62.0511111105240.20589@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <200511110925.48259.ioe-lkml@rameria.de>
On Fri, 11 Nov 2005, Ingo Oeser wrote:
> > I haven't even heard anyone mention a need for this in the past 1-2 years.
>
> Because the people need it are usally at the application level.
> It would be useful with hard disk editing.
>
> But this would need a move_blocks within the filesystem, which
> could attach a given list of blocks to another file.
>
> E.g. mremap() for files :-)
Something similar to that is included in my patch migration patchsets.
It will also allow you to selectively push pages in a range out. So it
does something similar to hole punching.
For that you would scan over the range to be cleared and put the pages on
a list using isolate_lru_page(). Then do whatever you need to with the
pages. Push em out with migrate_pages(list, NULL) etc.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2005-11-11 19:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 23:23 Badari Pulavarty
2005-11-10 23:32 ` Andrew Morton
2005-11-10 23:41 ` Badari Pulavarty
2005-11-10 23:55 ` Anton Altaparmakov
2005-11-11 8:25 ` Ingo Oeser
2005-11-11 19:07 ` Christoph Lameter [this message]
2005-11-16 12:08 ` Rob Landley
2005-11-16 12:20 ` Andrea Arcangeli
2005-11-13 15:09 ` Pavel Machek
2005-11-16 22:01 ` Badari Pulavarty
2005-11-16 23:37 ` Ric Wheeler
2005-11-21 6:46 ` Rob Landley
2005-11-18 16:42 ` Ragnar Kjørstad
2005-11-18 16:54 ` Badari Pulavarty
2005-11-11 5:18 ` Arjan van de Ven
2005-11-16 16:05 ` Badari Pulavarty
2005-11-16 16:38 ` Anton Altaparmakov
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=Pine.LNX.4.62.0511111105240.20589@schroedinger.engr.sgi.com \
--to=clameter@engr.sgi.com \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=hugh@veritas.com \
--cc=ioe-lkml@rameria.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pbadari@us.ibm.com \
/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