From: Lukas Czerner <lczerner@redhat.com>
To: linux-ext4@vger.kernel.org
Cc: enwlinux@gmail.com, Jose_Mario_Gallegos@Dell.com,
jordan_hargrave@Dell.com, rwheeler@redhat.com
Subject: [RFC PATCH 0/1] ext4: Try to better reuse recently freed space
Date: Thu, 4 Jul 2013 11:11:53 +0200 [thread overview]
Message-ID: <1372929114-12808-1-git-send-email-lczerner@redhat.com> (raw)
Hi all,
as I just recently discovered here http://www.ogris.de/blkalloc/ ext4 have
some unexpected allocation strategies which can cause some problems in
certain scenarios (see the 1/1 patch).
This is my attempt to fix this, however I think that this will need some
discussion because it changes some of the block allocator heuristic
quite significantly and I would like to make sure that it will not hurt
our performance in some widely used workloads. Eric, could you run your
performance testing with your test suite to see how it performs ?
Also, I think that the old behaviour might be quite helpful for SSD because
we're not overwriting existing blocks but rather trying to use new one, so
the firmware should have easier job. However I do not know how significant
impact if at all it might have. If we find out that this is helpful for
SSD we might make this conditional depending on the type of the device.
Which brings me to the other problem. Since the original behaviour is really
bad for thinly provisioned devices we would like to avoid using it even if
the underlying storage is SSD, however IIRC there is no way to distinguish
this from within the kernel.
See the comparison between the old and new allocator behaviour
http://people.redhat.com/lczerner/allocator/
Comments and testing is welcomed.
Thanks!
-Lukas
next reply other threads:[~2013-07-04 9:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 9:11 Lukas Czerner [this message]
2013-07-04 9:11 ` [RFC PATCH 1/1] ext4: Try to better reuse recently freed space Lukas Czerner
2013-07-04 15:09 ` Jan Kara
2013-07-04 15:32 ` Lukáš Czerner
2013-07-04 16:06 ` Jose_Mario_Gallegos
2013-07-08 7:38 ` [PATCH v2] " Lukas Czerner
2013-07-08 8:56 ` Jan Kara
2013-07-08 9:24 ` Lukáš Czerner
2013-07-08 11:59 ` Jan Kara
2013-07-08 21:27 ` Andreas Dilger
2013-07-10 11:30 ` Lukáš Czerner
2013-07-10 11:18 ` Lukáš Czerner
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=1372929114-12808-1-git-send-email-lczerner@redhat.com \
--to=lczerner@redhat.com \
--cc=Jose_Mario_Gallegos@Dell.com \
--cc=enwlinux@gmail.com \
--cc=jordan_hargrave@Dell.com \
--cc=linux-ext4@vger.kernel.org \
--cc=rwheeler@redhat.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;
as well as URLs for NNTP newsgroup(s).