From: Brian Foster <bfoster@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH v3 REPOST 0/2] xfs: set aside allocation btree blocks from block reservation
Date: Mon, 12 Apr 2021 09:30:57 -0400 [thread overview]
Message-ID: <20210412133059.1186634-1-bfoster@redhat.com> (raw)
Hi all,
There's been a decent amount of discussion on v3 of the series but
AFAIA, nothing that has materialized into changes to these two patches.
This is just a repost of v3 to bump the series.
Brian
v3: https://lore.kernel.org/linux-xfs/20210318161707.723742-1-bfoster@redhat.com/
- Use a mount flag for easy detection of active perag reservation.
- Filter rmapbt blocks from allocbt block accounting.
v2: https://lore.kernel.org/linux-xfs/20210222152108.896178-1-bfoster@redhat.com/
- Use an atomic counter instead of a percpu counter.
v1: https://lore.kernel.org/linux-xfs/20210217132339.651020-1-bfoster@redhat.com/
Brian Foster (2):
xfs: set a mount flag when perag reservation is active
xfs: set aside allocation btree blocks from block reservation
fs/xfs/libxfs/xfs_ag_resv.c | 24 ++++++++++++++----------
fs/xfs/libxfs/xfs_alloc.c | 12 ++++++++++++
fs/xfs/libxfs/xfs_alloc_btree.c | 2 ++
fs/xfs/xfs_mount.c | 18 +++++++++++++++++-
fs/xfs/xfs_mount.h | 7 +++++++
5 files changed, 52 insertions(+), 11 deletions(-)
--
2.26.3
next reply other threads:[~2021-04-12 13:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 13:30 Brian Foster [this message]
2021-04-12 13:30 ` [PATCH v3 1/2] xfs: set a mount flag when perag reservation is active Brian Foster
2021-04-14 0:49 ` Darrick J. Wong
2021-04-20 16:22 ` Brian Foster
2021-04-20 16:23 ` Brian Foster
2021-04-12 13:30 ` [PATCH v3 2/2] xfs: set aside allocation btree blocks from block reservation Brian Foster
2021-04-12 22:21 ` kernel test robot
2021-04-14 0:41 ` Darrick J. Wong
2021-04-19 0:59 ` [kbuild-all] " Chen, Rong A
2021-04-19 16:10 ` Darrick J. Wong
2021-04-14 1:00 ` Darrick J. Wong
2021-04-20 16:24 ` Brian Foster
2021-04-21 23:40 ` Darrick J. Wong
2021-04-22 12:41 ` 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=20210412133059.1186634-1-bfoster@redhat.com \
--to=bfoster@redhat.com \
--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).