From: Chris Mason <clm@fb.com>
To: David Sterba <dsterba@suse.cz>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH -rc2] btrfs: remove stale code after removing ordered operations
Date: Wed, 20 Aug 2014 11:09:21 -0400 [thread overview]
Message-ID: <53F4BA21.50705@fb.com> (raw)
In-Reply-To: <1408546994-4156-1-git-send-email-dsterba@suse.cz>
On 08/20/2014 11:03 AM, David Sterba wrote:
> The commit "btrfs: disable strict file flushes for renames and
> truncates" (8d875f95da43c6a8f18f77869f2ef26e9594fecc) left some unused
> code and defines.
See my followup for the perf regression, we still need these. I was
never able to trigger the enospc problem with xfstests here, but I did
double check that we're flushing or not properly now.
-chris
next prev parent reply other threads:[~2014-08-20 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 15:03 [PATCH -rc2] btrfs: remove stale code after removing ordered operations David Sterba
2014-08-20 15:09 ` Chris Mason [this message]
2014-08-20 15:34 ` [PATCH] btrfs: remove stale define " 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=53F4BA21.50705@fb.com \
--to=clm@fb.com \
--cc=dsterba@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).