From: Richard Wareing <rwareing@fb.com>
To: linux-xfs@vger.kernel.org
Cc: david@fromorbit.com, darrick.wong@oracle.com, hch@infradead.org
Subject: [PATCH v7 0/3] XFS realtime device tweaks
Date: Tue, 28 Nov 2017 13:55:24 -0800 [thread overview]
Message-ID: <20171128215527.2510350-1-rwareing@fb.com> (raw)
This is an nearly identical patch set to the v6 patch set. The only change is
a small tweak for the first patch in the series (see patch change log), and a
suitable update to the commit description/title for this patch.
Patch 1 in this series is independent and can be merged before the others.
There is some feedback requested for patch 2 in this series, re-posting from
v5/v6 cover letters to save some digging in your mailbox.
====
(from v5/v6 cover letter)
1. Inode flag now correctly set when locks are held via XFS_BMAPI_RTDATA
flag.
2. Realtime flag is honored when set by user via ioctl or inherit flag on
directory.
3. Misc changes around formatting & bounds checks on sysfs options.
See individual patches for more details.
Please pay close attention to the change in xfs_file_iomap_begin (patch 2),
the new version of the patch by-passes the xfs_file_iomap_begin_delay function
in the "realtime" case, since the realtime code here is not reachable/dead
(see assert in this function). Instead, we by-pass this, hit
xfs_iomap_write_direct where the XFS_BMAPI_RTDATA will be passed on to the
xfs_bmapi_write function where it's set.
I'm curious if there is a better approach, and/or verification this is
sane/safe.
Patch set based off Linux 4.14-rc8 (commit
39dae59d66acd86d1de24294bd2f343fd5e7a625) located @
https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git .
Richard Wareing (3):
xfs: Show realtime device stats on statfs calls if realtime flags set
xfs: Set realtime flag based on initial allocation size
xfs: Add realtime fallback if data device full
Documentation/filesystems/xfs.txt | 27 +++++++++++-
fs/xfs/libxfs/xfs_bmap.c | 35 +++++++++++++++
fs/xfs/libxfs/xfs_bmap.h | 3 ++
fs/xfs/xfs_bmap_util.c | 3 ++
fs/xfs/xfs_fsops.c | 2 +
fs/xfs/xfs_inode.c | 6 +++
fs/xfs/xfs_iomap.c | 18 +++++++-
fs/xfs/xfs_linux.h | 2 +
fs/xfs/xfs_mount.c | 24 +++++++++++
fs/xfs/xfs_mount.h | 8 ++++
fs/xfs/xfs_rtalloc.c | 90 +++++++++++++++++++++++++++++++++++++++
fs/xfs/xfs_rtalloc.h | 2 +
fs/xfs/xfs_super.c | 8 ++++
fs/xfs/xfs_sysfs.c | 80 ++++++++++++++++++++++++++++++++++
14 files changed, 305 insertions(+), 3 deletions(-)
--
2.9.5
next reply other threads:[~2017-11-28 21:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 21:55 Richard Wareing [this message]
2017-11-28 21:55 ` [PATCH v7 1/3] xfs: Show realtime device stats on statfs calls if realtime flags set Richard Wareing
2017-11-28 22:04 ` Darrick J. Wong
2017-11-28 21:55 ` [PATCH v7 2/3] xfs: Set realtime flag based on initial allocation size Richard Wareing
2017-11-28 21:55 ` [PATCH v7 3/3] xfs: Add realtime fallback if data device full Richard Wareing
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=20171128215527.2510350-1-rwareing@fb.com \
--to=rwareing@fb.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).