From: Dave Chinner <david@fromorbit.com>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2] xfs_io: support a basic extent swap command
Date: Fri, 9 Feb 2018 08:13:02 +1100 [thread overview]
Message-ID: <20180208211302.GE20266@dastard> (raw)
In-Reply-To: <20180208155719.17095-1-bfoster@redhat.com>
On Thu, Feb 08, 2018 at 10:57:19AM -0500, Brian Foster wrote:
> Extent swap is a low level mechanism exported by XFS to facilitate
> filesystem defragmentation. It is typically invoked by xfs_fsr under
> conditions that will atomically adjust inode extent state without
> loss of file data.
>
> While xfs_fsr provides some debug capability to tailor its behavior,
> it is not flexible enough to facilitate low level tests of the
> extent swap mechanism. For example, xfs_fsr may skip swaps between
> inodes that consist solely of preallocated extents because it
> considers such files already 100% defragmented. Further, xfs_fsr
> copies data between files where doing so may be unnecessary and thus
> inefficient for lower level tests.
>
> Add a basic swapext command to xfs_io that allows userspace
> invocation of the command under more controlled conditions. This
> facilites targeted tests without interference from xfs_fsr policy,
> such as using files with only preallocated extents, known/expected
> failure cases, etc. This command makes no effort to retain data
> across the operation. As such, it is for testing purposes only.
>
> Signed-off-by: Brian Foster <bfoster@redhat.com>
> ---
>
> v2:
> - Update xfs_io man page.
> - Fix up commit log description.
> v1: https://marc.info/?l=linux-xfs&m=151792224511355&w=2
Looks good. I'm no longer confused :)
Reviewed-by: Dave Chinner <dchinner@redhat.com>
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2018-02-08 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 15:57 [PATCH v2] xfs_io: support a basic extent swap command Brian Foster
2018-02-08 16:54 ` Darrick J. Wong
2018-02-08 21:13 ` Dave Chinner [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=20180208211302.GE20266@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.com \
--cc=linux-xfs@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 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).