public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs: a few performance improvements for fsync and rename/link
Date: Tue, 11 Aug 2020 12:43:28 +0100	[thread overview]
Message-ID: <20200811114328.688282-1-fdmanana@kernel.org> (raw)

From: Filipe Manana <fdmanana@suse.com>

A small group of changes to improve performance of fsync, rename and link operations.
They are farily independent, but patch 3 needs to be applied before patch 2, the
order can be changed if needed.
Details and performance tests are mentioned in the change log of each patch.

Filipe Manana (3):
  btrfs: do not take the log_mutex of the subvolume when pinning the log
  btrfs: do not commit logs and transactions during link and rename
    operations
  btrfs: make fast fsyncs wait only for writeback

 fs/btrfs/btrfs_inode.h  |   5 +
 fs/btrfs/file.c         |  97 +++++++++-----
 fs/btrfs/inode.c        | 115 ++---------------
 fs/btrfs/ordered-data.c |  59 +++++++++
 fs/btrfs/ordered-data.h |  11 ++
 fs/btrfs/transaction.c  |  10 ++
 fs/btrfs/transaction.h  |   7 ++
 fs/btrfs/tree-log.c     | 272 +++++++++++++++++++++-------------------
 fs/btrfs/tree-log.h     |  32 +++--
 9 files changed, 334 insertions(+), 274 deletions(-)

-- 
2.26.2


             reply	other threads:[~2020-08-11 11:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11 11:43 fdmanana [this message]
2020-08-19 14:08 ` [PATCH 0/3] btrfs: a few performance improvements for fsync and rename/link David Sterba
2020-08-19 14:23   ` Filipe Manana
2020-08-19 14:35     ` David Sterba

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=20200811114328.688282-1-fdmanana@kernel.org \
    --to=fdmanana@kernel.org \
    --cc=linux-btrfs@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