From: Brian Foster <bfoster@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org, Carlos Maiolino <cmaiolino@redhat.com>
Subject: Re: [PATCH REPOST 0/2] xfs: rely on minleft instead of total for bmbt res
Date: Mon, 21 Oct 2019 08:14:16 -0400 [thread overview]
Message-ID: <20191021121416.GA2953@bfoster> (raw)
In-Reply-To: <20191018171720.GB6719@magnolia>
On Fri, Oct 18, 2019 at 10:17:20AM -0700, Darrick J. Wong wrote:
> On Thu, Sep 12, 2019 at 10:32:21AM -0400, Brian Foster wrote:
> > 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?
>
> Any progress on this in the last month? I /think/ this is related to
> the unaligned allocations that Dan's complaining about this morning.
>
Not that I'm aware of. It looks similar and IIRC all that is really
needed here is a tweak to Carlos' and Dave's patch 1 that Carlos posted
(which replaces patch 1 of this series) added with patch 2 of this
series. I've just reposted a v2 series with that combination (including
links/references to hopefully reduce confusion).
Brian
> --D
>
> > 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
> >
prev parent reply other threads:[~2019-10-21 12:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 14:32 [PATCH REPOST 0/2] xfs: rely on minleft instead of total for bmbt res Brian Foster
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 [this message]
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=20191021121416.GA2953@bfoster \
--to=bfoster@redhat.com \
--cc=cmaiolino@redhat.com \
--cc=darrick.wong@oracle.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