From: Allison Henderson <achender@linux.vnet.ibm.com>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: Allison C Henderson <achender@us.ibm.com>,
Josef Bacik <josef@redhat.com>,
linux-ext4@vger.kernel.org, linux-ext4-owner@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Theodore Tso <tytso@mit.edu>
Subject: Re: ext2/3/4: punch support?
Date: Mon, 28 Feb 2011 19:19:14 -0700 [thread overview]
Message-ID: <4D6C57A2.3040500@linux.vnet.ibm.com> (raw)
In-Reply-To: <AANLkTikkDS38RhwP9LC47_Q-ZnUB_6q=EKRyQ8tswKW=@mail.gmail.com>
Alrighty then, I can send it out a little early since people are interested. It should show up here soon. Any feedback is appreciated! :)
Allison Henderson
On 2/28/2011 6:32 PM, Dave Young wrote:
> On Tue, Mar 1, 2011 at 8:44 AM, Allison C Henderson<achender@us.ibm.com> wrote:
>>
>> Hi All,
>>
>> I've actually already started on a patch set for punch hole support in ext4.
>> I've sent them out on the ltc-fsdev mailing list for review. I had planned
>> to spend another week or two running it through some more debug cases before
>> sending it to the ext4 mailing list though.
>
> Where can find your patch? should be sent to linux-ext4?
>
>>
>> linux-ext4-owner@vger.kernel.org wrote on 02/28/2011 06:11:18 AM:
>>
>>> Josef Bacik<josef@redhat.com>
>>> Sent by: linux-ext4-owner@vger.kernel.org
>>>
>>> 02/28/2011 06:11 AM
>>>
>>> To
>>>
>>> Dave Young<hidave.darkstar@gmail.com>
>>>
>>> cc
>>>
>>> josef@redhat.com, Theodore Tso<tytso@mit.edu>, linux-
>>> ext4@vger.kernel.org, Linux Kernel Mailing List
>>> <linux-kernel@vger.kernel.org>
>>>
>>> Subject
>>>
>>> Re: ext2/3/4: punch support?
>>>
>>> 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,
>>>
>>> Josef
>>> --
>>> 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 2:19 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
[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 [this message]
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=4D6C57A2.3040500@linux.vnet.ibm.com \
--to=achender@linux.vnet.ibm.com \
--cc=achender@us.ibm.com \
--cc=hidave.darkstar@gmail.com \
--cc=josef@redhat.com \
--cc=linux-ext4-owner@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).