From: Theodore Tso <tytso@mit.edu>
To: Mike Snitzer <snitzer@gmail.com>
Cc: Alex Buell <alex.buell@munted.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org
Subject: Re: Online ext4 defragmention
Date: Mon, 12 Jan 2009 09:15:39 -0500 [thread overview]
Message-ID: <20090112141539.GD21793@mit.edu> (raw)
In-Reply-To: <170fa0d20901120539w4e3bbc03na39f01edde206d25@mail.gmail.com>
On Mon, Jan 12, 2009 at 08:39:33AM -0500, Mike Snitzer wrote:
>
> Hi Ted,
>
> Could you elaborate on which allocation patches you're referring to in
> the ext4 patch queue (2.6.28-ext4-3?) ?
They haven't been implemented yet. They've been discussed on the ext4
mailing list, however. Basically, the Orlov algorithm was disabled
for flex_bg, and I want to optimize how directory blocks are allocated
to hopefully speed up fsck times a tad bit more. The design has been
roughly worked out; but it's a matter of me finding time to code and
test it...
- Ted
next prev parent reply other threads:[~2009-01-12 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 13:44 Online ext4 defragmention Alex Buell
2009-01-11 20:28 ` Theodore Tso
2009-01-12 13:39 ` Mike Snitzer
2009-01-12 14:15 ` Theodore Tso [this message]
2009-01-12 14:44 ` Mike Snitzer
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=20090112141539.GD21793@mit.edu \
--to=tytso@mit.edu \
--cc=alex.buell@munted.org.uk \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@gmail.com \
/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