linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: qgroups not enabled, but perf stats reports btrfs_qgroup_release_data and btrfs_qgroup_free_delayed_ref
Date: Mon, 8 Oct 2018 16:41:04 -0600	[thread overview]
Message-ID: <CAJCQCtQau7DtuUUeycCkZ36qjbKuxNzsgqJ7+sJ6W0dK_NLE3w@mail.gmail.com> (raw)

[chris@flap ~]$ sudo perf stat -e 'btrfs:*' -a sleep 70
##And then I loaded a few sites in Firefox early on in those 70 seconds.

 Performance counter stats for 'system wide':

                 5      btrfs:btrfs_transaction_commit
                29      btrfs:btrfs_inode_new
                29      btrfs:btrfs_inode_request
                25      btrfs:btrfs_inode_evict
             1,602      btrfs:btrfs_get_extent
                 0      btrfs:btrfs_handle_em_exist
                 1      btrfs:btrfs_get_extent_show_fi_regular
                88      btrfs:btrfs_truncate_show_fi_regular
                19      btrfs:btrfs_get_extent_show_fi_inline
                 2      btrfs:btrfs_truncate_show_fi_inline
               189      btrfs:btrfs_ordered_extent_add
               189      btrfs:btrfs_ordered_extent_remove
                 9      btrfs:btrfs_ordered_extent_start
               592      btrfs:btrfs_ordered_extent_put
             1,207      btrfs:__extent_writepage
             1,203      btrfs:btrfs_writepage_end_io_hook
                25      btrfs:btrfs_sync_file
                 0      btrfs:btrfs_sync_fs
                 0      btrfs:btrfs_add_block_group
             1,508      btrfs:add_delayed_tree_ref
             1,498      btrfs:run_delayed_tree_ref
               379      btrfs:add_delayed_data_ref
               336      btrfs:run_delayed_data_ref
             1,887      btrfs:add_delayed_ref_head
             1,839      btrfs:run_delayed_ref_head
                 0      btrfs:btrfs_chunk_alloc
                 0      btrfs:btrfs_chunk_free
               794      btrfs:btrfs_cow_block
             6,982      btrfs:btrfs_space_reservation
                 0      btrfs:btrfs_trigger_flush
                 0      btrfs:btrfs_flush_space
               952      btrfs:btrfs_reserved_extent_alloc
                 0      btrfs:btrfs_reserved_extent_free
             1,005      btrfs:find_free_extent
             1,005      btrfs:btrfs_reserve_extent
               816      btrfs:btrfs_reserve_extent_cluster
                 1      btrfs:btrfs_find_cluster
                 0      btrfs:btrfs_failed_cluster_setup
                 1      btrfs:btrfs_setup_cluster
             5,952      btrfs:alloc_extent_state
             6,034      btrfs:free_extent_state
               374      btrfs:btrfs_work_queued
               362      btrfs:btrfs_work_sched
               362      btrfs:btrfs_all_work_done
               116      btrfs:btrfs_ordered_sched
                 0      btrfs:btrfs_workqueue_alloc
                 0      btrfs:btrfs_workqueue_destroy
                 0      btrfs:btrfs_qgroup_reserve_data
               201      btrfs:btrfs_qgroup_release_data
             1,839      btrfs:btrfs_qgroup_free_delayed_ref
                 0      btrfs:btrfs_qgroup_account_extents
                 0      btrfs:btrfs_qgroup_trace_extent
                 0      btrfs:btrfs_qgroup_account_extent
                 0      btrfs:qgroup_update_counters
                 0      btrfs:qgroup_update_reserve
                 0      btrfs:qgroup_meta_reserve
                 0      btrfs:qgroup_meta_convert
                 0      btrfs:qgroup_meta_free_all_pertrans
                 0      btrfs:btrfs_prelim_ref_merge
                 0      btrfs:btrfs_prelim_ref_insert
             2,663      btrfs:btrfs_inode_mod_outstanding_extents
                 0      btrfs:btrfs_remove_block_group
                 0      btrfs:btrfs_add_unused_block_group
                 0      btrfs:btrfs_skip_unused_block_group

      70.004723586 seconds time elapsed

[chris@flap ~]$


Seems like a lot of activity for just a few transactions, but what
really caught my eye here is the qgroup reporting for a file system
that has never had qgroups enabled. Is it expected?


Chris Murphy

             reply	other threads:[~2018-10-08 22:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08 22:41 Chris Murphy [this message]
2018-10-09  3:21 ` qgroups not enabled, but perf stats reports btrfs_qgroup_release_data and btrfs_qgroup_free_delayed_ref Qu Wenruo

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=CAJCQCtQau7DtuUUeycCkZ36qjbKuxNzsgqJ7+sJ6W0dK_NLE3w@mail.gmail.com \
    --to=lists@colorremedies.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).