From: Josef Bacik <jbacik@fb.com>
To: Adam Gradzki <adam.gradzki@gmail.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-cleaner leaves CPU pinned to 100%
Date: Wed, 4 Dec 2013 09:49:09 -0800 [thread overview]
Message-ID: <20131204174909.GA6675@fb.com> (raw)
In-Reply-To: <loom.20131204T162331-814@post.gmane.org>
Adam Gradzki <adam.gradzki@gmail.com> wrote on Wed [2013-Dec-04 15:27:58 +0000]:
> Adam G <adam.gradzki <at> gmail.com> writes:
>
> >
> > Hello,
> >
> > After a recent kernel upgrade I noticed the fans blowing at full
> > throttle on my laptop.
> >
> > There is currently very low load on the machine and nothing out of the
> > ordinary has occurred to lead me to believe this is normal behavior.
> >
> > Here is a link to the perf output I managed to capture
> >
> > http://pastebin.com/a5cAy7Dw
> >
> > Please let me know if I may be of any further assistance.
> >
> > Regards,
> >
> > Adam Gradzki
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> > the body of a message to majordomo <at> vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> >
>
> I would like to add an updated perf report I took shortly after the first
> one yesterday (600 seconds this time).
>
> http://www.pastebin.ca/2492119
>
> Removing autodefrag from /etc/fstab has ameliorated my troubles for the time
> being.
>
Do you have a lot of snapshots? I'm working on this currently so hopefully it
will be fixed soon. If you have issues again can you use perf record -g so it
pulls the stacktraces and then you can drill down before you post so I can
figure out where we're spending all of our time. Thanks,
Josef
next prev parent reply other threads:[~2013-12-04 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 17:28 btrfs-cleaner leaves CPU pinned to 100% Adam G
2013-12-04 15:27 ` Adam Gradzki
2013-12-04 17:49 ` Josef Bacik [this message]
[not found] ` <CALnfhZAEg1EgtDmZ6Qka=Ka-oaUmg++3mN3M=qOf5BHtEXXPpA@mail.gmail.com>
2013-12-05 0:19 ` Adam G
2013-12-05 10:27 ` Duncan
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=20131204174909.GA6675@fb.com \
--to=jbacik@fb.com \
--cc=adam.gradzki@gmail.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