From: "Justin M. Forbes" <jforbes@redhat.com>
To: ming.lei@canonical.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: loop block-mq conversion scalability issues
Date: Thu, 23 Apr 2015 16:04:10 -0500 [thread overview]
Message-ID: <1429823050.26534.9.camel@redhat.com> (raw)
The block-mq conversion for loop in 4.0 kernels is showing us an
interesting scalability problem with live CDs (ro, squashfs). It was
noticed when testing the Fedora beta that the more CPUs a liveCD image
was given, the slower it would boot. A 4 core qemu instance or bare
metal instance took more than twice as long to boot compared to a single
CPU instance. After investigating, this came directly to the block-mq
conversion, reverting these 4 patches will return performance. More
details are available at
https://bugzilla.redhat.com/show_bug.cgi?id=1210857
I don't think that reverting the patches is the ideal solution so I am
looking for other options. Since you know this code a bit better than I
do I thought I would run it by you while I am looking as well.
Thanks,
Justin
next reply other threads:[~2015-04-23 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 21:04 Justin M. Forbes [this message]
2015-04-24 2:59 ` loop block-mq conversion scalability issues Ming Lei
2015-04-24 21:46 ` Justin M. Forbes
2015-04-25 10:32 ` Ming Lei
2015-04-26 15:27 ` Ming Lei
2015-04-27 13:48 ` Justin M. Forbes
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=1429823050.26534.9.camel@redhat.com \
--to=jforbes@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.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