linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@us.ibm.com>
To: akpm@osdl.org, andrea@suse.de, hugh@veritas.com
Cc: lkml <linux-kernel@vger.kernel.org>, linux-mm <linux-mm@kvack.org>
Subject: [RFC] sys_punchhole()
Date: Thu, 10 Nov 2005 15:23:14 -0800	[thread overview]
Message-ID: <1131664994.25354.36.camel@localhost.localdomain> (raw)

Hi Andrew,

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 ?
Or wait till need arises ? 

My thought line is, I would add a generic_zeroblocks_range() 
function which would zero out the given range of pages and 
flush to disk.  Use this as a default operation, if the 
filesystems doesn't provide a specific function to free up
the blocks. Would this work ?

Suggestions ?

Thanks,
Badari

--
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>

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

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-10 23:23 Badari Pulavarty [this message]
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
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=1131664994.25354.36.camel@localhost.localdomain \
    --to=pbadari@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=andrea@suse.de \
    --cc=hugh@veritas.com \
    --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