From: Peter Kieser <peter@kieser.ca>
To: linux-bcache@vger.kernel.org
Subject: Poor performance with qemu and bcache FUA
Date: Sat, 28 Mar 2015 09:49:57 -0700 [thread overview]
Message-ID: <5516DBB5.1070708@kieser.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
Hello,
I finally was able to track down the commit that was causing poor
performance with qemu and LVM or qcow2 backed storage on virtual
machines since 2013 that use barriers on their guest FS (the default.)
This was most obvious with tools like apt-get and installing
linux-headers (it would take ~8 minutes on my system with 2 Intel 530
SSDs in RAID1):
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-3.10.y&id=3fcbc17636c83da9d85e2604de4af56c215e6e3c
Looks like FUA implemented in bcache does not play nicely with qemu. I
reverted this commit, and now a single virtual machine is no longer able
to DoS all other virtual machines on the system. The symptoms would be
that the cache devices would be fully utilized with a small number of
writes.
Are there any plans to revisit this? I don't like the idea of leaving
FUA unadvertised as data loss could occur if there is a power failure.
Thank you,
-Peter
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4291 bytes --]
reply other threads:[~2015-03-28 16:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5516DBB5.1070708@kieser.ca \
--to=peter@kieser.ca \
--cc=linux-bcache@vger.kernel.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 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.