From: Stefan Hajnoczi <shajnocz@redhat.com>
To: Huaicheng Li <lhcwhu@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu AIO worker threads change causes Guest OS hangup
Date: Tue, 1 Mar 2016 16:34:04 -0500 (EST) [thread overview]
Message-ID: <1079134073.2531350.1456868044024.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <FD610E23-37F8-4C0C-987A-8CF254C82667@gmail.com>
----- Original Message -----
> From: "Huaicheng Li" <lhcwhu@gmail.com>
> I’m trying to add some latency conditionally to I/O requests (qemu_paiocb,
> from **IDE** disk emulation, **raw** image file).
Paolo already covered the technical issue with what you're doing.
Have you seen Linux Documentation/device-mapper/delay.txt?
You could set up a loopback block device and put the device-mapper delay target on top to simulate latency.
Stefan
next prev parent reply other threads:[~2016-03-01 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 18:45 [Qemu-devel] qemu AIO worker threads change causes Guest OS hangup Huaicheng Li
2016-03-01 21:01 ` Paolo Bonzini
2016-03-06 2:42 ` Huaicheng Li (coperd)
2016-03-07 13:02 ` Paolo Bonzini
2016-03-07 14:32 ` Huaicheng Li (coperd)
2016-03-01 21:34 ` Stefan Hajnoczi [this message]
2016-03-06 2:33 ` Huaicheng Li (coperd)
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=1079134073.2531350.1456868044024.JavaMail.zimbra@redhat.com \
--to=shajnocz@redhat.com \
--cc=lhcwhu@gmail.com \
--cc=qemu-devel@nongnu.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.