From: Dave Young <hidave.darkstar@gmail.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Josef Bacik <josef@redhat.com>, Theodore Tso <tytso@mit.edu>,
linux-ext4@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: ext2/3/4: punch support?
Date: Tue, 1 Mar 2011 09:27:40 +0800 [thread overview]
Message-ID: <AANLkTimntcYVCyVo3-GRhFKd2eCbBpRan4G8+hLSRyLZ@mail.gmail.com> (raw)
In-Reply-To: <4D6BBCA2.8030104@redhat.com>
On Mon, Feb 28, 2011 at 11:17 PM, Eric Sandeen <sandeen@redhat.com> wrote:
> On 2/28/11 8:29 AM, Dave Young wrote:
>> On Mon, Feb 28, 2011 at 9:11 PM, Josef Bacik <josef@redhat.com> wrote:
>>> On Mon, Feb 28, 2011 at 03:03:40PM +0800, Dave Young wrote:
>>>> Hi, josef and ext guys
>>>>
>>>> Do you have any plan with ext4 hole punching support? And the
>>>> fallocate for ext2/3?
>>>>
>>>> What's the obstacle to work on this? could someone tell the status of
>>>> this issue?
>>>
>>> There is no obstacle, just nobody has bothered to do it. If you want to do it
>>> go for it. Thanks,
>>
>> Yes, I want to do some kvm image space discard stuff,
>> I use ext4 as my filesystem, but currently only xfs support something
>> like trim/discard.
>
> As Lukas said, ext4 & ext3 support various forms of trim/discard already.
>
> But that's different from punch...
Lukas and Eric, thanks for pointing out, I think I means punch,
although trim/discard is
useful as well in guest side.
>
> And as for fallocate on ext3, you need somewhere to put the metadata to indicate a block is allocated but not written. This was a lot more straightforward for ext4, since it describes a large range of blocks with a single extent structure.
As for ext3 fallocate, I found some interesting discuss:
http://www.mail-archive.com/linux-ext4@vger.kernel.org/msg02371.html
Andrew, do you know what's the status of above issue?
>
> -Eric
>
>> I know general knowledge about ext filesystem, but nearly new to ext4 code,
>> could you give some hint where to start?
>>
>> --
>> Thanks
>> dave
>> --
>> 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
>
>
--
Regards
dave
--
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
next prev parent reply other threads:[~2011-03-01 1:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 7:03 ext2/3/4: punch support? Dave Young
2011-02-28 13:11 ` Josef Bacik
2011-02-28 14:29 ` Dave Young
2011-02-28 14:50 ` Lukas Czerner
2011-02-28 15:17 ` Eric Sandeen
2011-03-01 1:27 ` Dave Young [this message]
[not found] ` <OFF2910C77.5B46C8B2-ON87257846.000354EE-07257846.000414E9@us.ibm.com>
2011-03-01 1:32 ` Dave Young
2011-03-01 2:19 ` Allison Henderson
2011-03-01 2:26 ` Dave Young
2011-03-01 3:12 ` Allison Henderson
-- strict thread matches above, loose matches on Subject: below --
2011-03-01 0:59 Allison Henderson
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=AANLkTimntcYVCyVo3-GRhFKd2eCbBpRan4G8+hLSRyLZ@mail.gmail.com \
--to=hidave.darkstar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=josef@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).