From: David Sterba <dsterba@suse.cz>
To: Josef Bacik <josef@toxicpanda.com>
Cc: kernel-team@fb.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/2][v2] Rework the worst case calculations for space reservation
Date: Fri, 23 Aug 2019 15:03:03 +0200 [thread overview]
Message-ID: <20190823130303.GP2752@twin.jikos.cz> (raw)
In-Reply-To: <20190822191434.13800-1-josef@toxicpanda.com>
On Thu, Aug 22, 2019 at 03:14:32PM -0400, Josef Bacik wrote:
> v1->v2:
> - dropped "btrfs: global reserve fallback should use metadata_size", turns out
> I was testing without my evict changes in place so we don't even need this in
> the first place, but it is also wrong because we need to reserve space for the
> orphan item which is an insert.
As the evict patches are in misc-next now and this patchset applies
cleanly I'll add it directly to misc-next. Thanks.
prev parent reply other threads:[~2019-08-23 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 19:14 [PATCH 0/2][v2] Rework the worst case calculations for space reservation Josef Bacik
2019-08-22 19:14 ` [PATCH 1/2] btrfs: rename the btrfs_calc_*_metadata_size helpers Josef Bacik
2019-08-22 19:14 ` [PATCH 2/2] btrfs: only reserve metadata_size for inodes Josef Bacik
2019-08-23 13:03 ` David Sterba [this message]
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=20190823130303.GP2752@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox