From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
cmm@us.ibm.com, tytso@mit.edu, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Fix fallocate to update the file size in each transaction.
Date: Thu, 13 Mar 2008 09:04:19 -0500 [thread overview]
Message-ID: <47D93463.9040506@redhat.com> (raw)
In-Reply-To: <20080313075139.GI5851@webber.adilger.int>
Andreas Dilger wrote:
> On Mar 11, 2008 11:25 +0530, Aneesh Kumar K.V wrote:
>> + -x: run test after preallocating the area (1|2) 2 to not update size.\n\
>
> The issue with preallocating just a single area in fsx is that this isn't
> much different than starting the test with a single large write or truncate.
except that the filesystem does still have to manage the unwritten
extent splits properly... but I agree that ongoing extending and
non-extending fallocates of various sizes would be very interesting.
-Eric
> What would be a lot more useful is to have fsx continually do fallocate
> requests of variable sizes during the test. This would be quite similar
> to a "write" operation, except that it wouldn't change any existing data
> and holes would still read back as zero. The only difference is in the
> "do not update size" test any fallocate at the end of the file would not
> increase the file size.
>
> This would exercise the fallocate code a LOT because it would put unwritten
> extents in the middle of the file, map a single fallocate to multiple
> discontiguous holes of the file (not overwriting existing allocated data
> in the middle of the file), verify fallocate of an overlapping unwritten
> extent works, etc.
>
prev parent reply other threads:[~2008-03-13 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 5:47 [PATCH] ext4: Fix fallocate to update the file size in each transaction Aneesh Kumar K.V
2008-03-11 5:55 ` Aneesh Kumar K.V
2008-03-13 7:51 ` Andreas Dilger
2008-03-13 14:04 ` Eric Sandeen [this message]
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=47D93463.9040506@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@sun.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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