| To: | Theodore Ts'o <tytso@xxxxxxx> |
|---|---|
| Subject: | Re: [PATCH-v2 0/5] add support for a lazytime mount option |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Mon, 24 Nov 2014 01:07:55 -0800 |
| Cc: | linux-fsdevel@xxxxxxxxxxxxxxx, Ext4 Developers List <linux-ext4@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, linux-btrfs@xxxxxxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <1416675267-2191-1-git-send-email-tytso@xxxxxxx> |
| References: | <1416675267-2191-1-git-send-email-tytso@xxxxxxx> |
| User-agent: | Mutt/1.5.23 (2014-03-12) |
What's the test coverage for this? xfstest generic/192 tests that atime is persisted over remounts, which we had a bug with when XFS used to have a lazy atime implementation somewhat similar to the proposal. We should have something similar for c/mtime as well. Also a test to ensure timestamps are persisted afer a fsync, although right now I can't imagine how to do that genericly as no other filesystem seems to have an equivaent to XFS_IOC_GOINGDOWN. It seems you also handle i_version updates lazily. although that's not mentioned anywhere. I actually have a clarification request out on the IETF NFSv4 list about the persistance requirements for the change counter but I've not seen an answer to it yet. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH v6 10/10] xfstests: fsx: Add fallocate insert range operation, Namjae Jeon |
|---|---|
| Next by Date: | Re: [PATCH-v2 0/5] add support for a lazytime mount option, Theodore Ts'o |
| Previous by Thread: | [PATCH-v2 5/5] ext4: add support for a lazytime mount option, Theodore Ts'o |
| Next by Thread: | Re: [PATCH-v2 0/5] add support for a lazytime mount option, Theodore Ts'o |
| Indexes: | [Date] [Thread] [Top] [All Lists] |