From: David Sterba <dsterba@suse.cz>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH 0/5] Rework eviction space flushing
Date: Mon, 19 Aug 2019 18:20:37 +0200 [thread overview]
Message-ID: <20190819162036.GE24086@twin.jikos.cz> (raw)
In-Reply-To: <20190801221937.22742-1-josef@toxicpanda.com>
On Thu, Aug 01, 2019 at 06:19:32PM -0400, Josef Bacik wrote:
> This is a set of patches to address how we do space flushing for inode
> evictions. Historically we've only been allowed to do a few things to reclaim
> space for inode evictions, mostly because we'd deadlock with iput. But we have
> delayed iputs in place to make sure we're always doing iput where it's
> completely safe to do an iput.
>
> However we do run iputs for flushing, so we can't just do FLUSH_ALL, otherwise
> we could deadlock. Also we still want to prioritize evictions for space
> reclamation because we likely will free up space for other people to make
> reservations.
>
> The first 4 patches are preparation patches, just refactoring so we can add this
> new flushing time for eviction. This allows us to clean up our current ad-hoc
> loop we have for reclaiming space for evictions and use the common helpers that
> everybody else uses. Thanks,
1-5 added to misc-next, thanks.
prev parent reply other threads:[~2019-08-19 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 22:19 [PATCH 0/5] Rework eviction space flushing Josef Bacik
2019-08-01 22:19 ` [PATCH 1/5] btrfs: add a flush step for delayed iputs Josef Bacik
2019-08-01 22:19 ` [PATCH 2/5] btrfs: unify error handling for ticket flushing Josef Bacik
2019-08-01 22:19 ` [PATCH 3/5] btrfs: factor out the ticket flush handling Josef Bacik
2019-08-01 22:19 ` [PATCH 4/5] btrfs: refactor priority_reclaim_metadata_space Josef Bacik
2019-08-19 16:22 ` David Sterba
2019-08-01 22:19 ` [PATCH 5/5] btrfs: introduce an evict flushing state Josef Bacik
2019-08-05 17:50 ` [PATCH 0/5] Rework eviction space flushing David Sterba
2019-08-19 16:20 ` 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=20190819162036.GE24086@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;
as well as URLs for NNTP newsgroup(s).