From: "Jérôme Carretero" <cJ-ko@zougloub.eu>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: [weird] High CPU usage caused by btrfs-transaction thread busy doing find_next_zero_bit()
Date: Wed, 22 Feb 2012 11:20:21 -0500 [thread overview]
Message-ID: <20120222112021.2c8c4d4b@Malcolm> (raw)
Dear devs,
My filesystem is super-sluggish since about a week, and perf top tells me
that find_next_bit(), find_next_zero_bit() is eating my netbook's CPU.
The kernel is 3.3-rc3+188 (g3ec1e88) and I don't use this laptop a lot,
so I'm ready to cooperate.
In the btrfs-transaction thread, in descending order of CPU usage:
find_next_zero_bit, find_next_bit, rb_next, setup_cluster_bitmap,
setup_cluster_no_bitmap, tree_search_offset.
I'm on #btrfs (Zougloub)
Regards,
--
cJ
next reply other threads:[~2012-02-22 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 16:20 Jérôme Carretero [this message]
2012-03-15 3:16 ` [weird] High CPU usage caused by btrfs-transaction thread busy doing find_next_zero_bit() Jérôme Carretero
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=20120222112021.2c8c4d4b@Malcolm \
--to=cj-ko@zougloub.eu \
--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).