From: Theodore Ts'o <tytso@mit.edu>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [RFC PATCH 1/1] ext4: Try to better reuse recently freed space
Date: Wed, 4 Dec 2013 00:21:19 -0500 [thread overview]
Message-ID: <20131204052119.GD15658@thunk.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1312021727150.2284@localhost.localdomain>
On Mon, Dec 02, 2013 at 05:32:06PM +0100, Lukáš Czerner wrote:
> Hi all,
>
> this is the patch I send a while ago to fix the issue I've seen with
> a global allocation goal. This might no longer apply to the current
> kernel and it might not be the best approach, but I use this example
> just to start a discussion about those allocation goals and how to
> use, or change them.
>
> I think that we agree that the long term fix would be to have free
> extent map. But we might be able to do something quickly, unless
> someone commits to make the free extent map reality :)
There was discussion from the previous thread here:
http://patchwork.ozlabs.org/patch/257476/
Looking at this, I think the patch makes sense, but I think it would
be good if we started thinking about what would be some good
benchmarks so we can measure and compare various different allocation
strategies.
Part of it would certainly be how long it takes to write or fallocate
the files, but also how how fragmented the files are. Some indication
about how friendly the file system is to flash and thin-provisioned
systems. (Where re-using blocks sooner rather than later might be
helpful if the user is only running fstrim once a week or some such.)
- Ted
--
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:[~2013-12-04 5:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 16:32 [RFC PATCH 1/1] ext4: Try to better reuse recently freed space Lukáš Czerner
2013-12-04 5:21 ` Theodore Ts'o [this message]
2014-04-01 5:30 ` Theodore Ts'o
2014-04-01 11:44 ` Dmitry Monakhov
2014-04-01 14:47 ` Theodore Ts'o
2014-04-01 16:35 ` Dmitry Monakhov
2014-04-07 18:22 ` Andreas Dilger
2014-04-07 20:01 ` Andreas Dilger
2014-04-08 1:14 ` Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2013-07-04 9:11 [RFC PATCH 0/1] " Lukas Czerner
2013-07-04 9:11 ` [RFC PATCH 1/1] " Lukas Czerner
2013-07-04 15:09 ` Jan Kara
2013-07-04 15:32 ` Lukáš Czerner
2013-07-04 16:06 ` Jose_Mario_Gallegos
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=20131204052119.GD15658@thunk.org \
--to=tytso@mit.edu \
--cc=lczerner@redhat.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.