From: "Marcin Mirosław" <marcin@mejor.pl>
To: xen-devel@lists.xensource.com
Subject: Re: Re: [b.g.o.358549] blkfront: Move blkif_interrupt into a tasklet.
Date: Sat, 21 May 2011 15:57:13 +0200 [thread overview]
Message-ID: <4DD7C4B9.6070308@mejor.pl> (raw)
In-Reply-To: <4DC15DC8.2010302@mejor.pl>
Hi!
I've noticed kernel threads "flush-254:9" does 100%CPU utilization.
Device 254-9 is logical volume created via LVM.
I don't know if this problem is related to earlier problem, but it
happens on the same kernel as mentioned issue.
Regards,
Marcin.
next prev parent reply other threads:[~2011-05-21 13:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 14:08 [b.g.o.358549] blkfront: Move blkif_interrupt into a tasklet Marcin Mirosław
2011-05-05 21:22 ` Konrad Rzeszutek Wilk
2011-05-05 22:57 ` Marcin Mirosław
2011-05-05 23:03 ` Daniel Stodden
2011-05-05 23:07 ` Marcin Mirosław
2011-05-21 13:57 ` Marcin Mirosław [this message]
2011-05-24 13:13 ` Konrad Rzeszutek Wilk
2011-05-31 11:28 ` Marcin Mirosław
2011-06-27 14:13 ` Konrad Rzeszutek Wilk
2011-06-27 15:04 ` Marcin Mirosław
2011-06-27 17:30 ` Konrad Rzeszutek Wilk
2011-06-27 22:01 ` Marcin Mirosław
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=4DD7C4B9.6070308@mejor.pl \
--to=marcin@mejor.pl \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).