public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.17-rc6
Date: Fri, 25 Feb 2022 16:53:04 +0100	[thread overview]
Message-ID: <cover.1645801545.git.dsterba@suse.com> (raw)

Hi,

this is a hopefully last batch of fixes for defrag that got broken in
5.16, all stable material. The remaining reported problem is excessive
IO with autodefrag due to various conditions in the defrag code not met
or missing.

Please pull, thanks.

----------------------------------------------------------------
The following changes since commit 2e7be9db125a0bf940c5d65eb5c40d8700f738b5:

  btrfs: send: in case of IO error log it (2022-02-09 18:53:26 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.17-rc5-tag

for you to fetch changes up to 558732df2122092259ab4ef85594bee11dbb9104:

  btrfs: reduce extent threshold for autodefrag (2022-02-24 16:11:28 +0100)

----------------------------------------------------------------
Dāvis Mosāns (1):
      btrfs: prevent copying too big compressed lzo segment

Qu Wenruo (8):
      btrfs: defrag: allow defrag_one_cluster() to skip large extent which is not a target
      btrfs: defrag: don't try to merge regular extents with preallocated extents
      btrfs: defrag: don't defrag extents which are already at max capacity
      btrfs: defrag: remove an ambiguous condition for rejection
      btrfs: defrag: bring back the old file extent search behavior
      btrfs: defrag: don't use merged extent map for their generation check
      btrfs: autodefrag: only scan one inode once
      btrfs: reduce extent threshold for autodefrag

 fs/btrfs/ctree.h      |   2 +-
 fs/btrfs/extent_map.c |   2 +
 fs/btrfs/extent_map.h |   8 ++
 fs/btrfs/file.c       |  97 +++++++------------
 fs/btrfs/inode.c      |   4 +-
 fs/btrfs/ioctl.c      | 256 ++++++++++++++++++++++++++++++++++++++++++++++----
 fs/btrfs/lzo.c        |  11 +++
 7 files changed, 296 insertions(+), 84 deletions(-)

             reply	other threads:[~2022-02-25 15:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25 15:53 David Sterba [this message]
2022-02-25 22:15 ` [GIT PULL] Btrfs fixes for 5.17-rc6 pr-tracker-bot

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=cover.1645801545.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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