From: Nikolay Borisov <nborisov@suse.com>
To: Josef Bacik <josef@toxicpanda.com>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH 15/23] btrfs: use ticketing for data space reservations
Date: Tue, 7 Jul 2020 17:46:54 +0300 [thread overview]
Message-ID: <63ed5861-0728-662a-20c1-03e60a59ee25@suse.com> (raw)
In-Reply-To: <20200630135921.745612-16-josef@toxicpanda.com>
On 30.06.20 г. 16:59 ч., Josef Bacik wrote:
> Now that we have all the infrastructure in place, use the ticketing
> infrastructure to make data allocations. This still maintains the exact
> same flushing behavior, but now we're using tickets to get our
> reservations satisfied.
>
> Reviewed-by: Nikolay Borisov <nborisov@suse.com>
> Tested-by: Nikolay Borisov <nborisov@suse.com>
> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
> ---
> fs/btrfs/space-info.c | 125 ++++++++++++++++++++++--------------------
> 1 file changed, 67 insertions(+), 58 deletions(-)
>
> diff --git a/fs/btrfs/space-info.c b/fs/btrfs/space-info.c
> index 799ee6090693..ee4747917b81 100644
> --- a/fs/btrfs/space-info.c
> +++ b/fs/btrfs/space-info.c
> @@ -1068,6 +1068,54 @@ static void priority_reclaim_metadata_space(struct btrfs_fs_info *fs_info,
> } while (flush_state < states_nr);
> }
>
> +static void priority_reclaim_data_space(struct btrfs_fs_info *fs_info,
> + struct btrfs_space_info *space_info,
> + struct reserve_ticket *ticket,
> + const enum btrfs_flush_state *states,
> + int states_nr)
> +{
> + int flush_state = 0;
> + int commit_cycles = 2;
> +
> + while (!space_info->full) {
> + flush_space(fs_info, space_info, U64_MAX, ALLOC_CHUNK_FORCE);
> + spin_lock(&space_info->lock);
> + if (ticket->bytes == 0) {
> + spin_unlock(&space_info->lock);
> + return;
> + }
> + spin_unlock(&space_info->lock);
> + }
> +again:
> + while (flush_state < states_nr) {
> + u64 flush_bytes = U64_MAX;
> +
> + if (!commit_cycles) {
> + if (states[flush_state] == FLUSH_DELALLOC_WAIT) {
> + flush_state++;
> + continue;
> + }
> + if (states[flush_state] == COMMIT_TRANS)
> + flush_bytes = ticket->bytes;
> + }
> +
> + flush_space(fs_info, space_info, flush_bytes,
> + states[flush_state]);
> + spin_lock(&space_info->lock);
> + if (ticket->bytes == 0) {
> + spin_unlock(&space_info->lock);
> + return;
> + }
> + spin_unlock(&space_info->lock);
> + flush_state++;
> + }
> + if (commit_cycles) {
> + commit_cycles--;
> + flush_state = 0;
> + goto again;
> + }
> +}
> +
> static void wait_reserve_ticket(struct btrfs_fs_info *fs_info,
> struct btrfs_space_info *space_info,
> struct reserve_ticket *ticket)
> @@ -1134,6 +1182,15 @@ static int handle_reserve_ticket(struct btrfs_fs_info *fs_info,
> evict_flush_states,
> ARRAY_SIZE(evict_flush_states));
> break;
> + case BTRFS_RESERVE_FLUSH_DATA:
> + priority_reclaim_data_space(fs_info, space_info, ticket,
> + data_flush_states,
> + ARRAY_SIZE(data_flush_states));
> + break;
> + case BTRFS_RESERVE_FLUSH_FREE_SPACE_INODE:
> + priority_reclaim_data_space(fs_info, space_info, ticket,
> + NULL, 0);
> + break;
> default:
> ASSERT(0);
> break;
> @@ -1341,78 +1398,30 @@ int btrfs_reserve_data_bytes(struct btrfs_fs_info *fs_info, u64 bytes,
> enum btrfs_reserve_flush_enum flush)
> {
> struct btrfs_space_info *data_sinfo = fs_info->data_sinfo;
> - const enum btrfs_flush_state *states = NULL;
> u64 used;
> - int states_nr = 0;
> - int commit_cycles = 2;
> int ret = -ENOSPC;
>
> ASSERT(!current->journal_info || flush != BTRFS_RESERVE_FLUSH_DATA);
>
> - if (flush == BTRFS_RESERVE_FLUSH_DATA) {
> - states = data_flush_states;
> - states_nr = ARRAY_SIZE(data_flush_states);
> - }
> -
> spin_lock(&data_sinfo->lock);
> -again:
> used = btrfs_space_info_used(data_sinfo, true);
>
> if (used + bytes > data_sinfo->total_bytes) {
> - u64 prev_total_bytes = data_sinfo->total_bytes;
> - int flush_state = 0;
> + struct reserve_ticket ticket;
>
> + init_waitqueue_head(&ticket.wait);
> + ticket.bytes = bytes;
> + ticket.error = 0;
> + list_add_tail(&ticket.list, &data_sinfo->priority_tickets);
nit: Shouldn't adding the ticket also be recorded in
spac_info->reclaim_size?
I see later that you are removing this code and relying on the existing
logic in __reserve_metadata_bytes( renamed to reserve_bytes) which
correctly modifies reclaim_size, but this just means this particular
patch is slightly broken.
> spin_unlock(&data_sinfo->lock);
>
> - /*
> - * Everybody can force chunk allocation, so try this first to
> - * see if we can just bail here and make our reservation.
> - */
> - flush_space(fs_info, data_sinfo, bytes, ALLOC_CHUNK_FORCE);
> - spin_lock(&data_sinfo->lock);
> - if (prev_total_bytes < data_sinfo->total_bytes)
> - goto again;
> + ret = handle_reserve_ticket(fs_info, data_sinfo, &ticket,
> + flush);
> + } else {
> + btrfs_space_info_update_bytes_may_use(fs_info, data_sinfo, bytes);
> + ret = 0;
<snip>
next prev parent reply other threads:[~2020-07-07 14:47 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 13:58 [PATCH 00/23] Change data reservations to use the ticketing infra Josef Bacik
2020-06-30 13:58 ` [PATCH 01/23] btrfs: change nr to u64 in btrfs_start_delalloc_roots Josef Bacik
2020-06-30 13:59 ` [PATCH 02/23] btrfs: remove orig from shrink_delalloc Josef Bacik
2020-06-30 13:59 ` [PATCH 03/23] btrfs: handle U64_MAX for shrink_delalloc Josef Bacik
2020-06-30 13:59 ` [PATCH 04/23] btrfs: make shrink_delalloc take space_info as an arg Josef Bacik
2020-06-30 13:59 ` [PATCH 05/23] btrfs: make ALLOC_CHUNK use the space info flags Josef Bacik
2020-06-30 13:59 ` [PATCH 06/23] btrfs: call btrfs_try_granting_tickets when freeing reserved bytes Josef Bacik
2020-06-30 13:59 ` [PATCH 07/23] btrfs: call btrfs_try_granting_tickets when unpinning anything Josef Bacik
2020-06-30 13:59 ` [PATCH 08/23] btrfs: call btrfs_try_granting_tickets when reserving space Josef Bacik
2020-06-30 13:59 ` [PATCH 09/23] btrfs: use the btrfs_space_info_free_bytes_may_use helper for delalloc Josef Bacik
2020-06-30 13:59 ` [PATCH 10/23] btrfs: use btrfs_start_delalloc_roots in shrink_delalloc Josef Bacik
2020-06-30 13:59 ` [PATCH 11/23] btrfs: check tickets after waiting on ordered extents Josef Bacik
2020-06-30 13:59 ` [PATCH 12/23] btrfs: add flushing states for handling data reservations Josef Bacik
2020-06-30 13:59 ` [PATCH 13/23] btrfs: add the data transaction commit logic into may_commit_transaction Josef Bacik
2020-07-07 14:39 ` Nikolay Borisov
2020-07-07 14:54 ` Josef Bacik
2020-07-07 15:01 ` Josef Bacik
2020-06-30 13:59 ` [PATCH 14/23] btrfs: add btrfs_reserve_data_bytes and use it Josef Bacik
2020-06-30 13:59 ` [PATCH 15/23] btrfs: use ticketing for data space reservations Josef Bacik
2020-07-07 14:46 ` Nikolay Borisov [this message]
2020-07-07 14:56 ` Josef Bacik
2020-06-30 13:59 ` [PATCH 16/23] btrfs: serialize data reservations if we are flushing Josef Bacik
2020-06-30 13:59 ` [PATCH 17/23] btrfs: use the same helper for data and metadata reservations Josef Bacik
2020-06-30 13:59 ` [PATCH 18/23] btrfs: drop the commit_cycles stuff for data reservations Josef Bacik
2020-06-30 13:59 ` [PATCH 19/23] btrfs: don't force commit if we are data Josef Bacik
2020-06-30 13:59 ` [PATCH 20/23] btrfs: run delayed iputs before committing the transaction for data Josef Bacik
2020-06-30 13:59 ` [PATCH 21/23] btrfs: flush delayed refs when trying to reserve data space Josef Bacik
2020-06-30 13:59 ` [PATCH 22/23] btrfs: do async reclaim for data reservations Josef Bacik
2020-06-30 13:59 ` [PATCH 23/23] btrfs: add a comment explaining the data flush steps Josef Bacik
2020-07-03 16:30 ` [PATCH 00/23] Change data reservations to use the ticketing infra David Sterba
2020-07-07 15:28 ` Josef Bacik
-- strict thread matches above, loose matches on Subject: below --
2020-07-21 14:22 [PATCH 00/23][v4] " Josef Bacik
2020-07-21 14:22 ` [PATCH 15/23] btrfs: use ticketing for data space reservations Josef Bacik
2020-08-13 16:50 ` David Sterba
2020-08-13 16:51 ` David Sterba
2020-08-13 17:12 ` David Sterba
2020-07-08 13:59 [PATCH 00/23][v3] Change data reservations to use the ticketing infra Josef Bacik
2020-07-08 14:00 ` [PATCH 15/23] btrfs: use ticketing for data space reservations Josef Bacik
2020-07-07 15:42 [PATCH 00/23][v2] Change data reservations to use the ticketing infra Josef Bacik
2020-07-07 15:42 ` [PATCH 15/23] btrfs: use ticketing for data space reservations Josef Bacik
2020-02-04 16:19 [PATCH 0/23][v4] Convert data reservations to the ticketing infrastructure Josef Bacik
2020-02-04 16:19 ` [PATCH 15/23] btrfs: use ticketing for data space reservations Josef Bacik
2020-02-04 17:04 ` Johannes Thumshirn
2020-01-31 22:35 [PATCH 00/23][v2] Convert data reservations to the ticketing infrastructure Josef Bacik
2020-01-31 22:36 ` [PATCH 15/23] btrfs: use ticketing for data space reservations Josef Bacik
2020-02-03 14:29 ` Nikolay Borisov
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=63ed5861-0728-662a-20c1-03e60a59ee25@suse.com \
--to=nborisov@suse.com \
--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