From: "Madhusudhan" <madhu.cr@ti.com>
To: linux-mmc@vger.kernel.org
Cc: linux-omap@vger.kernel.org, 'Pierre Ossman' <pierre@ossman.eu>,
hch@lst.de
Subject: mmcqd cpu utilization
Date: Wed, 2 Sep 2009 12:23:59 -0500 [thread overview]
Message-ID: <007301ca2bf2$2888e2a0$544ff780@am.dhcp.ti.com> (raw)
Hi,
Has anyone monitored the cpu utilization percentage when a MMC/SD card is in
use? I have noticed that mmc_queue_thread "mmcqd" consumes a lot of cpu
cycles in a periodic fashion. What I mean here is that I see spikes of high
cpu utilization due to mmcqd. There will a cp or similar which will be
already consuming cpu to transfer data to the MMC/SD device. Further mmcqd
increases that load randomly to a high number.
Has anyone seen similar behavior? Any thoughts?
Regards,
Madhu
next reply other threads:[~2009-09-02 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 17:23 Madhusudhan [this message]
2009-09-02 17:40 ` mmcqd cpu utilization Pierre Ossman
2009-09-02 19:57 ` Madhusudhan
2009-09-02 20:00 ` Dasgupta, Romit
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='007301ca2bf2$2888e2a0$544ff780@am.dhcp.ti.com' \
--to=madhu.cr@ti.com \
--cc=hch@lst.de \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pierre@ossman.eu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.