From: Rob Landley <rob@landley.net>
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: Wed, 16 Nov 2005 06:08:18 -0600 [thread overview]
Message-ID: <200511160608.18413.rob@landley.net> (raw)
In-Reply-To: <200511110925.48259.ioe-lkml@rameria.de>
On Friday 11 November 2005 02:25, Ingo Oeser wrote:
> 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).
You know, if you wanted to get really really gross and disgusting about this,
you could always have write(fd, NULL, count) punch a hole in the file. (Then
have libc's write() check for NULL and error out, and have a seprate punch()
call that does the write with the null...)
Just one way to avoid introducing a new syscall...
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Landley <rob@landley.net>
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: Wed, 16 Nov 2005 06:08:18 -0600 [thread overview]
Message-ID: <200511160608.18413.rob@landley.net> (raw)
In-Reply-To: <200511110925.48259.ioe-lkml@rameria.de>
On Friday 11 November 2005 02:25, Ingo Oeser wrote:
> 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).
You know, if you wanted to get really really gross and disgusting about this,
you could always have write(fd, NULL, count) punch a hole in the file. (Then
have libc's write() check for NULL and error out, and have a seprate punch()
call that does the write with the null...)
Just one way to avoid introducing a new syscall...
Rob
--
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-16 12:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 23:23 [RFC] sys_punchhole() Badari Pulavarty
2005-11-10 23:23 ` Badari Pulavarty
2005-11-10 23:32 ` Andrew Morton
2005-11-10 23:32 ` Andrew Morton
2005-11-10 23:41 ` Badari Pulavarty
2005-11-10 23:41 ` Badari Pulavarty
2005-11-10 23:55 ` Anton Altaparmakov
2005-11-10 23:55 ` Anton Altaparmakov
2005-11-11 8:25 ` Ingo Oeser
2005-11-11 19:07 ` Christoph Lameter
2005-11-11 19:07 ` Christoph Lameter
2005-11-16 12:08 ` Rob Landley [this message]
2005-11-16 12:08 ` Rob Landley
2005-11-16 12:20 ` Andrea Arcangeli
2005-11-16 12:20 ` Andrea Arcangeli
2005-11-13 15:09 ` Pavel Machek
2005-11-13 15:09 ` Pavel Machek
2005-11-16 22:01 ` Badari Pulavarty
2005-11-16 22:01 ` Badari Pulavarty
2005-11-16 23:37 ` Ric Wheeler
2005-11-16 23:37 ` Ric Wheeler
2005-11-21 6:46 ` Rob Landley
2005-11-21 6:46 ` Rob Landley
2005-11-18 16:42 ` Ragnar Kjørstad
2005-11-18 16:42 ` Ragnar Kjørstad
2005-11-18 16:54 ` Badari Pulavarty
2005-11-18 16:54 ` Badari Pulavarty
2005-11-11 5:18 ` Arjan van de Ven
2005-11-11 5:18 ` Arjan van de Ven
2005-11-13 6:11 ` H. Peter Anvin
2005-11-16 16:05 ` Badari Pulavarty
2005-11-16 16:05 ` Badari Pulavarty
2005-11-16 16:38 ` Anton Altaparmakov
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=200511160608.18413.rob@landley.net \
--to=rob@landley.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.