From: Tao Ma <tao.ma@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: mfasheh@suse.com, Joel Becker <joel.becker@oracle.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 00/15] replace barriers with explicit flush / FUA usage
Date: Fri, 20 Aug 2010 14:50:34 +0800 [thread overview]
Message-ID: <4C6E25BA.2020009@oracle.com> (raw)
In-Reply-To: <20100818105307.GA31992@infradead.org>
On 08/18/2010 06:53 PM, Christoph Hellwig wrote:
> On Wed, Aug 18, 2010 at 03:35:42AM -0700, Joel Becker wrote:
>> On Wed, Aug 18, 2010 at 05:29:08AM -0400, Christoph Hellwig wrote:
>>> This series converts over all filesystems to the new WRITE_FLUSH_FUA
>>> primitive that Tejun added. XFS, btrfs, gfs2, reiserfs, ext3 and ext4
>>> have passed extensive xfstests coverage with this, while ocfs2, nilfs2
>>> and fat are unsupposed by xfstests and thus untested in this patch.
>>
>> What does it take to get ocfs2 supported by xfstests?
>
> Basically just a few filesystem-specific paramters need to be added
> to the switch table in common.rc:
>
> - mkfs paramters if the default mkfs.$FSTYPE invocation doesn't do the
> right thing, or ask for confirmatio when doing things like
> overwriting existing filesystems or working on whole disks (not sure
> if anyone but extN came up with that last weird thing)
> - mount paramters for a successfull single node mount with acls and
> xattrs enabled
> - fsck options to actually force a real check even if the filesystem
> is mounted clean (and is nessecary to not make it wait for user
> input)
> - optionally an entry to create a filesystem with a given size for
> ENOSPC tests.
oh, I didn't noticed that you have described in detail here.
Sorry for the noise.
Regards,
Tao
next prev parent reply other threads:[~2010-08-20 6:51 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 9:29 [PATCH 00/15] replace barriers with explicit flush / FUA usage Christoph Hellwig
2010-08-18 9:29 ` [PATCH 01/15] kill BH_Ordered flag Christoph Hellwig
2010-08-18 9:29 ` [PATCH 02/15] pass gfp_mask and flags to sb_issue_discard Christoph Hellwig
2010-08-20 1:23 ` Mike Snitzer
2010-08-18 9:29 ` [PATCH 03/15] xfs: replace barriers with explicit flush / FUA usage Christoph Hellwig
2010-08-18 23:47 ` Dave Chinner
2010-08-18 9:29 ` [PATCH 04/15] btrfs: " Christoph Hellwig
2010-08-18 12:06 ` Chris Mason
2010-08-18 9:29 ` [PATCH 05/15] gfs2: " Christoph Hellwig
2010-08-18 10:08 ` Steven Whitehouse
2010-08-18 13:37 ` Bob Peterson
2010-08-18 9:29 ` [PATCH 06/15] reiserfs: " Christoph Hellwig
2010-08-18 13:16 ` Jan Kara
2010-08-18 13:21 ` Chris Mason
2010-08-18 9:29 ` [PATCH 07/15] nilfs2: " Christoph Hellwig
2010-08-18 13:31 ` Ryusuke Konishi
2010-08-18 13:41 ` Christoph Hellwig
2010-08-18 9:29 ` [PATCH 08/15] jbd: " Christoph Hellwig
2010-08-18 13:07 ` Jan Kara
2010-08-18 9:29 ` [PATCH 09/15] jbd2: " Christoph Hellwig
2010-08-18 14:03 ` Jan Kara
2010-08-18 14:09 ` Christoph Hellwig
2010-08-18 9:29 ` [PATCH 10/15] ext4: do not send discards as barriers Christoph Hellwig
2010-08-18 13:28 ` Jan Kara
2010-08-18 9:29 ` [PATCH 11/15] fat: " Christoph Hellwig
2010-08-18 9:29 ` [PATCH 12/15] swap: " Christoph Hellwig
2010-08-19 3:47 ` Hugh Dickins
2010-08-19 4:08 ` Nigel Cunningham
2010-08-19 9:02 ` Christoph Hellwig
2010-08-19 11:35 ` Chris Mason
2010-08-22 12:20 ` Nigel Cunningham
2010-08-18 9:29 ` [PATCH 13/15] remove the WRITE_BARRIER flag Christoph Hellwig
2010-08-18 9:29 ` [PATCH 14/15] remove the BLKDEV_IFL_BARRIER flag Christoph Hellwig
2010-08-20 1:26 ` Mike Snitzer
2010-08-18 9:29 ` [PATCH 15/15] remove the BH_Eopnotsupp flag Christoph Hellwig
2010-08-18 10:35 ` [PATCH 00/15] replace barriers with explicit flush / FUA usage Joel Becker
2010-08-18 10:53 ` Christoph Hellwig
2010-08-20 6:50 ` Tao Ma [this message]
2010-08-18 15:11 ` Ted Ts'o
2010-08-18 16:46 ` Christoph Hellwig
2010-08-20 4:00 ` Tao Ma
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=4C6E25BA.2020009@oracle.com \
--to=tao.ma@oracle.com \
--cc=hch@infradead.org \
--cc=joel.becker@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mfasheh@suse.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).