From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH v2 0/3] xfs: support removal of multi-record inode chunks
Date: Mon, 20 Jun 2016 13:12:01 -0400 [thread overview]
Message-ID: <1466442724-13544-1-git-send-email-bfoster@redhat.com> (raw)
Hi all,
This is an old series I'm dusting off that helps extend XFS' typical
dynamic inode chunk behavior to large block size filesystems. While XFS
currently supports such large block sizes, we don't ever remove inode
records on filesystems with a block size large enough such that a single
block covers more than one inode chunk.
This has been tested on ppc64 with a 64k block size and on other arches
(x86-64, i386) with more standard 4k blocksize configurations.
Brian
v2:
- Rebase to latest for-next.
v1: http://oss.sgi.com/pipermail/xfs/2015-May/041814.html
Brian Foster (3):
xfs: create helper to delete multiple inobt records
xfs: remove entire inode chunks when all inodes are free
xfs: inobt record insert/delete tracepoints
fs/xfs/libxfs/xfs_ialloc.c | 270 +++++++++++++++++++++++++++++++++++++++++----
fs/xfs/xfs_trace.h | 32 ++++++
2 files changed, 281 insertions(+), 21 deletions(-)
--
2.5.5
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-06-20 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 17:12 Brian Foster [this message]
2016-06-20 17:12 ` [PATCH v2 1/3] xfs: create helper to delete multiple inobt records Brian Foster
2016-06-20 17:12 ` [PATCH v2 2/3] xfs: remove entire inode chunks when all inodes are free Brian Foster
2016-06-20 17:12 ` [PATCH v2 3/3] xfs: inobt record insert/delete tracepoints 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=1466442724-13544-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