public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH v2 0/2] xfs: rely on minleft instead of total for bmbt res
Date: Mon, 21 Oct 2019 08:13:20 -0400	[thread overview]
Message-ID: <20191021121322.25659-1-bfoster@redhat.com> (raw)

This is a v2 that is a combination of two series. Patch 1 is Carlos' and
Dave's patch [1] (that replaces my original patch 1) with an additional
modification based on discussion with Dave [2] in the original v1 post
of this series. Patch 2 is a repost from my previous v1 [3].

Note that this combination of changes is currently untested AFAIA. I'm
planning to run through some tests today and will report back on any
issues...

Brian

v2:
- Added xfs_bmap_btalloc() changes to patch 1.

[1] https://lore.kernel.org/linux-xfs/20190918082453.25266-2-cmaiolino@redhat.com/
[2] https://lore.kernel.org/linux-xfs/20190914220035.GY16973@dread.disaster.area/
[3] https://lore.kernel.org/linux-xfs/20190912143223.24194-3-bfoster@redhat.com/

Brian Foster (1):
  xfs: don't set bmapi total block req where minleft is sufficient

Dave Chinner (1):
  xfs: cap longest free extent to maximum allocatable

 fs/xfs/libxfs/xfs_alloc.c |  3 ++-
 fs/xfs/libxfs/xfs_bmap.c  | 19 +++++++++----------
 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 +--
 7 files changed, 20 insertions(+), 21 deletions(-)

-- 
2.20.1


             reply	other threads:[~2019-10-21 12:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 12:13 Brian Foster [this message]
2019-10-21 12:13 ` [PATCH v2 1/2] xfs: cap longest free extent to maximum allocatable Brian Foster
2019-10-22 16:16   ` Darrick J. Wong
2019-10-21 12:13 ` [PATCH v2 2/2] xfs: don't set bmapi total block req where minleft is sufficient Brian Foster
2019-10-22 16:51   ` Darrick J. Wong
2019-10-22 17:10     ` 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=20191021121322.25659-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