From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH v2 0/8] speculative preallocation inode tracking
Date: Mon, 10 Sep 2012 14:37:18 -0400 [thread overview]
Message-ID: <1347302246-52710-1-git-send-email-bfoster@redhat.com> (raw)
Hi all,
This is v2 of the speculative preallocation inode tracking patchset. This
functionality tracks inodes with post-EOF speculative preallocation for the
purpose of background and on-demand trimming.
Background scanning occurs on a longish interval (5 minutes by default) and in
a best-effort mode (i.e., inodes are skipped due to lock contention or dirty
cache). The intent is to clear up post-EOF blocks on inodes that might have
allocations hanging around due to open-write-close sequences (NFS).
On demand scanning is provided via a new ioctl and supports various parameters
such as scan mode, filtering by quota id and minimum file size. A pending use
case for on demand scanning is for accurate quota accounting via the gluster
scale out filesystem (i.e., to free up preallocated space when near a usage
limit).
Brian
v2:
- Remove unnecessary inode flag clear helper.
- Condense eofblocks set/clear tag functions.
- Move clear tag call into xfs_free_eofblocks().
- Modify AG walk infrastructure to support tag-based walk and utilize this
functionality for the eofblocks scan (as opposed to the previous code
duplicated from reclaim scanning).
- Improve ioctl functionality: new data structure fields/flags, validate quota
is enabled.
- Increase default background scanning interval to 5 minutes, add tunable.
Brian Foster (8):
xfs: add EOFBLOCKS inode tagging/untagging
xfs: support a tag-based inode_ag_iterator
xfs: create helper to check whether to free eofblocks on inode
xfs: export xfs_free_eofblocks() and return EAGAIN on trylock failure
xfs: create function to scan and clear EOFBLOCKS inodes
xfs: add XFS_IOC_FREE_EOFBLOCKS ioctl
xfs: add enhanced filtering to EOFBLOCKS scan
xfs: add background scanning to clear EOFBLOCKS inodes
fs/xfs/xfs_ag.h | 1 +
fs/xfs/xfs_fs.h | 23 +++++
fs/xfs/xfs_globals.c | 1 +
fs/xfs/xfs_ioctl.c | 20 ++++
fs/xfs/xfs_iomap.c | 7 ++
fs/xfs/xfs_iops.c | 3 +
fs/xfs/xfs_linux.h | 1 +
fs/xfs/xfs_mount.h | 2 +
fs/xfs/xfs_qm_syscalls.c | 5 +-
fs/xfs/xfs_sync.c | 215 ++++++++++++++++++++++++++++++++++++++++++++--
fs/xfs/xfs_sync.h | 11 ++-
fs/xfs/xfs_sysctl.c | 9 ++
fs/xfs/xfs_sysctl.h | 1 +
fs/xfs/xfs_trace.h | 6 ++
fs/xfs/xfs_vnodeops.c | 27 +++---
fs/xfs/xfs_vnodeops.h | 24 +++++-
16 files changed, 327 insertions(+), 29 deletions(-)
--
1.7.7.6
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-09-10 18:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 18:37 Brian Foster [this message]
2012-09-10 18:37 ` [PATCH v2 1/8] xfs: add EOFBLOCKS inode tagging/untagging Brian Foster
2012-09-10 18:37 ` [PATCH v2 2/8] xfs: support a tag-based inode_ag_iterator Brian Foster
2012-09-10 18:37 ` [PATCH v2 3/8] xfs: create helper to check whether to free eofblocks on inode Brian Foster
2012-09-11 5:27 ` Dave Chinner
2012-09-10 18:37 ` [PATCH v2 4/8] xfs: export xfs_free_eofblocks() and return EAGAIN on trylock failure Brian Foster
2012-09-10 18:37 ` [PATCH v2 5/8] xfs: create function to scan and clear EOFBLOCKS inodes Brian Foster
2012-09-10 18:37 ` [PATCH v2 6/8] xfs: add XFS_IOC_FREE_EOFBLOCKS ioctl Brian Foster
2012-09-10 18:37 ` [PATCH v2 7/8] xfs: add enhanced filtering to EOFBLOCKS scan Brian Foster
2012-09-10 18:37 ` [PATCH v2 8/8] xfs: add background scanning to clear EOFBLOCKS inodes 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=1347302246-52710-1-git-send-email-bfoster@redhat.com \
--to=bfoster@redhat.com \
--cc=xfs@oss.sgi.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