From: Brian Foster <bfoster@redhat.com>
To: linux-xfs@vger.kernel.org
Cc: Carlos Maiolino <cmaiolino@redhat.com>
Subject: [PATCH REPOST 0/2] xfs: rely on minleft instead of total for bmbt res
Date: Thu, 12 Sep 2019 10:32:21 -0400 [thread overview]
Message-ID: <20190912143223.24194-1-bfoster@redhat.com> (raw)
Hi all,
This is a repost of a couple patches I posted a few months ago[1]. There
are no changes other than a rebase to for-next. Any thoughts on these? I
think Carlos had also run into some related generic/223 failures fairly
recently...
Carlos,
Any chance you could give these a try?
Brian
[1] https://lore.kernel.org/linux-xfs/20190501140504.16435-1-bfoster@redhat.com/
Brian Foster (2):
xfs: drop minlen before tossing alignment on bmap allocs
xfs: don't set bmapi total block req where minleft is sufficient
fs/xfs/libxfs/xfs_bmap.c | 13 +++++++++----
fs/xfs/xfs_bmap_util.c | 4 ++--
fs/xfs/xfs_dquot.c | 4 ++--
fs/xfs/xfs_iomap.c | 4 ++--
fs/xfs/xfs_reflink.c | 4 ++--
fs/xfs/xfs_rtalloc.c | 3 +--
6 files changed, 18 insertions(+), 14 deletions(-)
--
2.20.1
next reply other threads:[~2019-09-12 14:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 14:32 Brian Foster [this message]
2019-09-12 14:32 ` [PATCH REPOST 1/2] xfs: drop minlen before tossing alignment on bmap allocs Brian Foster
2019-09-12 22:35 ` Dave Chinner
2019-09-12 22:46 ` Dave Chinner
2019-09-13 14:58 ` Brian Foster
2019-09-14 22:00 ` Dave Chinner
2019-09-15 13:09 ` Brian Foster
2019-09-16 8:36 ` Carlos Maiolino
2019-09-17 12:22 ` Carlos Maiolino
2019-09-18 21:41 ` Darrick J. Wong
2019-09-19 11:49 ` Brian Foster
2019-09-12 14:32 ` [PATCH REPOST 2/2] xfs: don't set bmapi total block req where minleft is sufficient Brian Foster
2019-09-18 21:55 ` Darrick J. Wong
2019-09-19 11:55 ` Brian Foster
2019-09-16 8:18 ` [PATCH REPOST 0/2] xfs: rely on minleft instead of total for bmbt res Carlos Maiolino
2019-10-18 17:17 ` Darrick J. Wong
2019-10-21 12:14 ` 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=20190912143223.24194-1-bfoster@redhat.com \
--to=bfoster@redhat.com \
--cc=cmaiolino@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.