From: James Cloos <cloos@jhcloos.com>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: 2.6.33 high cpu usage
Date: Tue, 02 Mar 2010 15:12:59 -0500 [thread overview]
Message-ID: <m3635e32jg.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <20100302195322.GA3201@localhost.localdomain> (Josef Bacik's message of "Tue, 2 Mar 2010 14:53:23 -0500")
>>>>> "Josef" == Josef Bacik <josef@redhat.com> writes:
>> As you can see btrfs_find_space_cluster(), find_next_bit() and
>> find_next_zero_bit() use most of the sys cpu. That patterns seems to
>> hold whenever I run perf top during such operations.
Josef> Ok well thats a bummer. Would you mind trying this completely untested
Josef> and uncompiled patch :)?
It is compiling now. I might not be able to reboot until tonight. And
I'll want to do another incremental backup of the fs. (I'm using it in
production in part because it only has mirrors, checkouts and the like
and because I have that backup.)
I'll reply again once I have results.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2010-03-02 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 18:35 2.6.33 high cpu usage James Cloos
2010-03-02 19:53 ` Josef Bacik
2010-03-02 20:12 ` James Cloos [this message]
2010-03-04 21:46 ` James Cloos
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=m3635e32jg.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=josef@redhat.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