linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: madhu.cr@ti.com (Madhusudhan)
To: linux-arm-kernel@lists.infradead.org
Subject: mmcqd seem to use lot of cpu cycles
Date: Tue, 1 Sep 2009 12:18:31 -0500	[thread overview]
Message-ID: <001401ca2b28$3a99bac0$544ff780@am.dhcp.ti.com> (raw)

Hi,

While running one of the MMC use cases in the system I saw that mmcqd seems
to eat up a lot of cpu cycles. I saw a thread which discussed some details.

http://www.nabble.com/mmcqd-uses-a-large-amount-of-cpu-td23768078.html

Any clue on what this process is doing? If a low level driver is using DMA I
am not sure why there is so much load on the system due to mmcqd? Any
thoughts?

 
Regards,
Madhu

             reply	other threads:[~2009-09-01 17:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-01 17:18 Madhusudhan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-09-01 17:12 mmcqd seem to use lot of cpu cycles Madhusudhan

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='001401ca2b28$3a99bac0$544ff780@am.dhcp.ti.com' \
    --to=madhu.cr@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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).