From: Dave Chinner <david@fromorbit.com>
To: fstests@vger.kernel.org
Subject: Re: [PATCH] xfs: new EOF fragmentation tests
Date: Mon, 11 Feb 2019 12:55:40 +1100 [thread overview]
Message-ID: <20190211015540.GD20493@dastard> (raw)
In-Reply-To: <20190211013647.22580-1-david@fromorbit.com>
On Mon, Feb 11, 2019 at 12:36:47PM +1100, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> These tests create substantial file fragmentation as a result of
> application actions that defeat post-EOF preallocation
> optimisations. They are intended to replicate known vectors for
> these problems, and provide a check that the fragmentation levels
> have been controlled. The mitigations we make may not completely
> remove fragmentation (e.g. they may demonstrate speculative delalloc
> related extent size growth) so the checks don't assume we'll end up
> with perfect layouts and hence check for an exceptable level of
> fragmentation rather than none.
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> ---
Forgot to add that these tests go along with this patch series:
https://marc.info/?l=linux-xfs&m=154951612101291&w=2
And can be used to test whatever way we decide to minimise
fragmentation through maintianing post-EOF preallocation.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-02-11 1:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 1:36 [PATCH] xfs: new EOF fragmentation tests Dave Chinner
2019-02-11 1:55 ` Dave Chinner [this message]
2019-02-12 14:03 ` Brian Foster
2019-02-12 21:04 ` Dave Chinner
2019-02-13 13:39 ` Brian Foster
2019-02-16 10:04 ` Eryu Guan
2019-02-17 21:56 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2024-06-23 5:38 xfs post-EOF block freeing fixes Christoph Hellwig
2024-06-23 5:38 ` [PATCH] xfs: new EOF fragmentation tests Christoph Hellwig
2024-06-23 13:03 ` Zorro Lang
2024-06-24 8:49 ` Christoph Hellwig
2024-09-24 8:45 xfs post-EOF block freeing fixes v2 Christoph Hellwig
2024-09-24 8:45 ` [PATCH] xfs: new EOF fragmentation tests Christoph Hellwig
2024-09-24 15:03 ` Darrick J. Wong
2024-09-25 11:15 ` Zorro Lang
2024-09-26 12:31 ` Zorro Lang
2024-10-01 14:59 ` Darrick J. Wong
2024-10-02 13:38 ` Zorro Lang
2024-10-02 14:35 ` Brian Foster
2024-10-02 14:57 ` Darrick J. Wong
2024-10-02 15:56 ` Brian Foster
2024-10-02 20:04 ` Darrick J. Wong
2024-10-13 17:49 ` Zorro Lang
2024-10-14 6:07 ` Christoph Hellwig
2024-10-14 14:14 ` Zorro Lang
2024-10-14 15:24 ` Darrick J. Wong
2024-10-14 17:46 ` Zorro Lang
2024-10-15 3:39 ` Christoph Hellwig
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=20190211015540.GD20493@dastard \
--to=david@fromorbit.com \
--cc=fstests@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.