public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <pierre@ossman.eu>
To: Madhusudhan <madhu.cr@ti.com>
Cc: linux-mmc@vger.kernel.org, linux-omap@vger.kernel.org, hch@lst.de
Subject: Re: mmcqd cpu utilization
Date: Wed, 2 Sep 2009 19:40:36 +0200	[thread overview]
Message-ID: <20090902194036.07c1f72c@mjolnir.ossman.eu> (raw)
In-Reply-To: <007301ca2bf2$2888e2a0$544ff780@am.dhcp.ti.com>

[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]

On Wed, 2 Sep 2009 12:23:59 -0500
"Madhusudhan" <madhu.cr@ti.com> wrote:

> 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?
> 

My guess would be that the omap driver doesn't (cannot?) use the
hardware to wait for busy to end, so the system must poll.

Anything better than that guess will require some profiling. :)

Rgds
-- 
     -- Pierre Ossman

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2009-09-02 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 17:23 mmcqd cpu utilization Madhusudhan
2009-09-02 17:40 ` Pierre Ossman [this message]
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=20090902194036.07c1f72c@mjolnir.ossman.eu \
    --to=pierre@ossman.eu \
    --cc=hch@lst.de \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=madhu.cr@ti.com \
    /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