public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: fstests@vger.kernel.org
Subject: [PATCH 0/3] generic: fixes for different allocation behaviours
Date: Thu, 14 May 2015 11:53:34 +1000	[thread overview]
Message-ID: <1431568417-6462-1-git-send-email-david@fromorbit.com> (raw)

Hi folks,

These 3 patches address failures I found when testing the XFS DAX
functionality. DAX disables delayed allocation on XFS, so the size
of the buffer in the write() call determines the size of the
allocation that is done. Hence tests that expect a specific extent
layout need to do IO in buffers as large as the extent size they
expect to be created.

The other side of this is that some tests also expect partial writes
to occur, which happened as a side effect of buffered writes being
broken down into PAGE_SIZE chunks. With DAX, that does not happen -
the writes tend to either succeed or fail completely, especially if
it is an ENOSPC condition that is ocurring.

HEnce these patches address these test assumptions, and now they
work correctly and pass on both DAX and non-DAX filesystems.

Cheers,

Dave.

             reply	other threads:[~2015-05-14  1:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14  1:53 Dave Chinner [this message]
2015-05-14  1:53 ` [PATCH 1/3] generic/018: use xfs_io and larger buffers for writes Dave Chinner
2015-05-14  1:53 ` [PATCH 2/3] generic/223, xfs/203: IO is not well aligned Dave Chinner
2015-05-14  1:53 ` [PATCH 3/3] generic/275: writes may not partially succeed Dave Chinner
2015-05-19 12:23 ` [PATCH 0/3] generic: fixes for different allocation behaviours Brian Foster

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=1431568417-6462-1-git-send-email-david@fromorbit.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox