All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Filipe Manana <fdmanana@suse.com>, <clm@fb.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [GIT PULL] Send fixes for 4.2
Date: Tue, 9 Jun 2015 15:17:28 +0800	[thread overview]
Message-ID: <55769308.1070803@cn.fujitsu.com> (raw)
In-Reply-To: <1433301319-515-1-git-send-email-fdmanana@suse.com>

Hi, Chris and Filipe.

Would you consider the patch from Filipe to be merged into 4.2?

[PATCH] Btrfs: avoid syncing log in the fast fsync path when not necessary

https://patchwork.kernel.org/patch/6138811/


The performance regression is already in 4.1, and I really don't like to
see the performance regression be there for 4.2.

So please consider include this patch in 4.2 merge window.

Thanks,
Qu

> Hi Chris,
>
> Please pull 2 fixes for the send feature from my branch send_fixes_4.2.
> Both have been around in the mailing list/patchwork before the 4.1 merge
> window opened but were not picked for 4.1. They both have tests merged
> in xfstests (btrfs/087 and btrfs/092), which as expected, fail without
> this fixes applied and pass with them applied.
>
> The following changes since commit c65b99f046843d2455aa231747b5a07a999a9f3d:
>
>    Linux 4.1-rc6 (2015-05-31 19:01:07 -0700)
>
> are available in the git repository at:
>
>    git://git.kernel.org/pub/scm/linux/kernel/git/fdmanana/linux.git send_fixes_4.2
>
> for you to fetch changes up to 8b191a684968e24b34c9894024b37532c68e6ae8:
>
>    Btrfs: incremental send, check if orphanized dir inode needs delayed rename (2015-06-03 03:10:40 +0100)
>
> ----------------------------------------------------------------
> Filipe Manana (2):
>        Btrfs: incremental send, don't delay directory renames unnecessarily
>        Btrfs: incremental send, check if orphanized dir inode needs delayed rename
>
>   fs/btrfs/send.c | 104 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---------------------
>   1 file changed, 83 insertions(+), 21 deletions(-)
>

  parent reply	other threads:[~2015-06-09  7:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03  3:15 [GIT PULL] Send fixes for 4.2 Filipe Manana
2015-06-03  3:15 ` [PATCH 1/2 RESEND] Btrfs: incremental send, don't delay directory renames unnecessarily Filipe Manana
2015-06-03  3:15 ` [PATCH 2/2 RESEND] Btrfs: incremental send, check if orphanized dir inode needs delayed rename Filipe Manana
2015-06-04  2:45 ` [GIT PULL] Send fixes for 4.2 Chris Mason
2015-06-09  7:17 ` Qu Wenruo [this message]
2015-06-09 13:02   ` Chris Mason

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=55769308.1070803@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=clm@fb.com \
    --cc=fdmanana@suse.com \
    --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 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.