From: Phillip Susi <psusi@ubuntu.com>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [RFC] ext4: block reservation allocation
Date: Sun, 11 Mar 2012 13:32:34 -0400 [thread overview]
Message-ID: <4F5CE1B2.80501@ubuntu.com> (raw)
In-Reply-To: <CAGpXXZ+z-HVECg+EAe4-d20BkjhX7bjxaHOs2_KBbgQaJwpCHQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/10/2012 07:26 PM, Greg Freemyer wrote:
>> I thought this could be done with the new defrag api. I thought it had a
>> way to allocate a new donor file in a specific location so you could then
>> migrate the target file to those specific donor blocks.
>>
>>
> I'm not aware of that ability in the defrag api.
>
> There are ohsm patches to do things along those lines, but they haven't
> been updated since 2.6.30 days as far as I know.
It seems this ability would be vital to e4defrag. Without it, it would end up being no better than filesystem agnostic defragmenters like shake. I'm almost certain there was some discussion in this direction a few years ago when e4defrag started being talked about, was it really not implemented?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPXOGuAAoJEJrBOlT6nu75n5kIANngR3o+ZQ6vij+jJ7nj1/S1
nTmWUA70328xZD/Ht2G/ue3oTqOnQmxDIFOhM8AuUoZ0fHondSRXRFpPsXyUU7LO
uc/ZranjqGCAH7IP3FzduqvOcQSJS8Vo4CI9bjrH0fnB7uV+vYbB0mVkVh7X2AHi
T/1h0KIbtna8T7n1ISb3xqvKDY1zUM5qR9a7qo5fHkZpgLBDQNDxu1Q1qMEiytet
HPksKZcPPvkA8oOuHvika1zj2FiidWWcmPsv20P80BtTaRUBmAHbc3s3Wox3THWh
SP0tI0260LiMEyVVSpdsx76NoV9lFpu0ezNOtFHjFL99lnCV2K/fsHpTaICDBiA=
=E6n5
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2012-03-11 17:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 9:09 [RFC] ext4: block reservation allocation Zheng Liu
2012-02-27 12:00 ` Lukas Czerner
2012-02-27 13:18 ` Zheng Liu
2012-02-27 13:33 ` Lukas Czerner
2012-02-27 15:09 ` Zheng Liu
2012-02-27 15:16 ` Lukas Czerner
2012-02-27 15:24 ` Lukas Czerner
2012-02-28 3:34 ` Zheng Liu
2012-02-27 21:16 ` Andreas Dilger
2012-02-27 13:36 ` Yongqiang Yang
2012-02-27 21:11 ` Andreas Dilger
2012-02-27 15:37 ` Eric Sandeen
2012-02-27 17:44 ` Ted Ts'o
2012-02-27 22:00 ` Andreas Dilger
2012-02-28 4:05 ` Zheng Liu
2012-03-08 16:39 ` Phillip Susi
[not found] ` <CAGpXXZ+z-HVECg+EAe4-d20BkjhX7bjxaHOs2_KBbgQaJwpCHQ@mail.gmail.com>
2012-03-11 17:32 ` Phillip Susi [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=4F5CE1B2.80501@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=greg.freemyer@gmail.com \
--cc=linux-ext4@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.