From: Tao Ma <tm@tao.ma>
To: Ted Ts'o <tytso@mit.edu>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: big allocation status
Date: Sat, 04 Jun 2011 16:34:09 +0800 [thread overview]
Message-ID: <4DE9EE01.6070406@tao.ma> (raw)
In-Reply-To: <20110604033805.GD2614@thunk.org>
On 06/04/2011 11:38 AM, Ted Ts'o wrote:
> On Fri, Jun 03, 2011 at 09:57:23AM +0800, Tao Ma wrote:
>> Hi Ted,
>>
>> Do you have any new branch or patch set that can be used for testing
>> about big allocation? The latest patch set in the mailist is what you
>> have sent at the beginning of May. Do you have an updated one? We will
>> try to test it soon and it would grateful if we are on the same page.
>
> There is a patch set available at:
>
> git://repo.or.cz/ext4-patch-queue.git
>
> The bigalloc patches are after the stable-boundary, and will apply
> against 3.0-rc1.
Great thanks, we will schedule some test maybe next week.
>
> Note that I've fixed them up so that they apply on top of the punch
> changes; however, the punch ioctl will not work correctly if bigalloc
> is enabled, since that hasn't been fixed up yet.
Fine, our test cases will not use punch ioctl AFAIK.
>
> Also, I'm still working on the e2fsprogs support.
Cool, but do you have a mkfs.ext4 that we can let the kernel part work
happily? Or we have to add the feature by hand by editing the disk
format. ;)
Regards,
Tao
next prev parent reply other threads:[~2011-06-04 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 1:57 big allocation status Tao Ma
2011-06-04 3:38 ` Ted Ts'o
2011-06-04 8:34 ` Tao Ma [this message]
2011-06-04 19:11 ` Ted Ts'o
2011-06-06 23:04 ` Ted Ts'o
2011-06-07 2:01 ` Tao Ma
2011-06-27 10:25 ` Tao Ma
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=4DE9EE01.6070406@tao.ma \
--to=tm@tao.ma \
--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;
as well as URLs for NNTP newsgroup(s).