linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ric Wheeler <ric@emc.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Pavel Machek <pavel@suse.cz>, Andrew Morton <akpm@osdl.org>,
	andrea@suse.de, hugh@veritas.com,
	lkml <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC] sys_punchhole()
Date: Wed, 16 Nov 2005 18:37:59 -0500	[thread overview]
Message-ID: <437BC2D7.3080003@emc.com> (raw)
In-Reply-To: <1132178470.24066.85.camel@localhost.localdomain>

Badari Pulavarty wrote:

>On Sun, 2005-11-13 at 15:09 +0000, Pavel Machek wrote:
>  
>
>>Hi!
>>
>>    
>>
>>>>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.
>>>      
>>>
>>Some database people wanted it maybe month ago. It was replaced by some 
>>madvise hack...
>>    
>>
>
>Hmm. Someone other than me asking for it ? 
>
>I did the madvise() hack and asking to see if any one really needs
>sys_punchole().
>
>Thanks,
>Badari
>
>
>  
>
I think that sys_punchole() would be useful for some object based 
storage systems.

Specifically, when you have a box that is trying to store potentially a 
billion objects on one file system, pushing several objects into a file 
("container") can be useful to keep the object count down.  The punch 
hole would be useful in reclaiming space in this type of scheme.

On the other side of the argument, you can argue that file systems that 
support large file counts and really big directories should perform well 
enough to make this use case less important.

ric


--
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-16 23:37 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
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 [this message]
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=437BC2D7.3080003@emc.com \
    --to=ric@emc.com \
    --cc=akpm@osdl.org \
    --cc=andrea@suse.de \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pavel@suse.cz \
    --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