From: Ingo Oeser <ioe-lkml@rameria.de>
To: linux-kernel@vger.kernel.org
Cc: 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 09:25:41 +0100 [thread overview]
Message-ID: <200511110925.48259.ioe-lkml@rameria.de> (raw)
In-Reply-To: <20051110153254.5dde61c5.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
Hi,
On Friday 11 November 2005 00:32, Andrew Morton wrote:
> Badari Pulavarty <pbadari@us.ibm.com> wrote:
> >
> > We discussed this in madvise(REMOVE) thread - to add support
> > for sys_punchhole(fd, offset, len) to complete the functionality
> > (in the future).
> >
> > http://marc.theaimsgroup.com/?l=linux-mm&m=113036713810002&w=2
> >
> > What I am wondering is, should I invest time now to do it ?
>
> 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 :-)
Both together would make harddisk video editing with linux quite
performant and less error prone.
Regards
Ingo Oeser
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-11-11 8:25 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 [this message]
2005-11-11 19:07 ` Christoph Lameter
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=200511110925.48259.ioe-lkml@rameria.de \
--to=ioe-lkml@rameria.de \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=hugh@veritas.com \
--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