From: Suparna Bhattacharya <suparna@in.ibm.com>
To: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Cc: "Amit K. Arora" <aarora@linux.vnet.ibm.com>,
Mingming Cao <cmm@US.IBM.COM>,
linux-ext4@vger.kernel.org, suzuki@in.ibm.com
Subject: Re: [RFC][Patch 1/1] Persistent preallocation in ext4
Date: Wed, 13 Dec 2006 21:08:38 +0530 [thread overview]
Message-ID: <20061213153838.GB7193@in.ibm.com> (raw)
In-Reply-To: <1166016989.5059.13.camel@kleikamp.austin.ibm.com>
On Wed, Dec 13, 2006 at 07:36:29AM -0600, Dave Kleikamp wrote:
> On Wed, 2006-12-13 at 15:31 +0530, Amit K. Arora wrote:
> > On Tue, Dec 12, 2006 at 04:20:38PM -0800, Mingming Cao wrote:
> > > On Tue, 2006-12-12 at 11:53 +0530, Amit K. Arora wrote:
>
> > > Supporting preallocation for extent based files seems fairly
> > > straightforward. I agree we should look at this first. After get this
> > > done, it probably worth re-consider whether to support preallocation for
> > > non-extent based files on ext4. I could imagine user upgrade from ext3
> > > to ext4, and expecting to use preallocation on those existing files....
>
> I disagree here. Why add the complexity for what is going to be a rare
> case? In cases where a user is going to benefit from preallocation,
> she'll probably also benefit from extents, and would be better off
> making a copy of the file, thus converting it to extents.
>
> > I gave a thought on this initially. But, I was not sure how we should
> > implement preallocation in a non-extent based file. Using extents we can
> > mark a set of blocks as unitialized, but how will we do this for
> > non-extent based files ? If we do not have a way to mark blocks
> > uninitialized, when someone will try to read from a preallocated block,
> > it will return junk/stale data instead of zeroes.
>
> If anything, the block-based preallocation could initialize all of the
> data to zero. It would be slow, but it would still provide the correct
> function and result in contiguous allocation.
And posix_fallocate does that already ...
Regards
Suparna
>
> Shaggy
> --
> David Kleikamp
> IBM Linux Technology Center
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Suparna Bhattacharya (suparna@in.ibm.com)
Linux Technology Center
IBM Software Lab, India
next prev parent reply other threads:[~2006-12-13 15:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 13:43 [RFC][Patch 1/1] Persistent preallocation in ext4 Amit K. Arora
2006-12-06 5:58 ` Amit K. Arora
2006-12-12 1:28 ` Mingming Cao
2006-12-12 6:23 ` Amit K. Arora
2006-12-13 0:20 ` Mingming Cao
2006-12-13 10:01 ` Amit K. Arora
2006-12-13 13:36 ` Dave Kleikamp
2006-12-13 15:38 ` Suparna Bhattacharya [this message]
2006-12-13 15:54 ` Mingming Cao
2006-12-15 12:35 ` [RFC][Patch 1/2] " Amit K. Arora
2006-12-19 11:05 ` Amit K. Arora
[not found] ` <20061219211206.GO5937@schatzie.adilger.int>
2006-12-20 6:28 ` Amit K. Arora
2006-12-27 23:30 ` Mingming Cao
2007-01-02 11:04 ` Amit K. Arora
2007-01-02 22:47 ` Mingming Cao
2007-01-09 9:05 ` Amit K. Arora
2006-12-15 12:39 ` [RFC][Patch 2/2] " Amit K. Arora
2006-12-15 23:02 ` Andreas Dilger
2006-12-16 4:30 ` Amit K. Arora
2006-12-19 11:42 ` Amit K. Arora
2006-12-19 11:54 ` Amit K. Arora
2006-12-19 21:14 ` Andreas Dilger
2006-12-19 21:23 ` Eric Sandeen
2006-12-20 8:19 ` Amit K. Arora
2006-12-22 15:16 ` Amit K. Arora
2006-12-22 15:31 ` Alex Tomas
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=20061213153838.GB7193@in.ibm.com \
--to=suparna@in.ibm.com \
--cc=aarora@linux.vnet.ibm.com \
--cc=cmm@US.IBM.COM \
--cc=linux-ext4@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.com \
--cc=suzuki@in.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;
as well as URLs for NNTP newsgroup(s).