From: DUO Labs <dvdugo333@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Question] [Block] Is there a way to control the read caching of a block device?
Date: Tue, 3 Sep 2024 14:13:18 -0400 [thread overview]
Message-ID: <d5f6c856-169d-4dcd-acd3-d42d886df17f@gmail.com> (raw)
I know that the `cache` parameter for `-drive` controls the caching behavior when writing from the guest to the host, but is there a way to control the reading behavior host->guest? Currently, on HEAD, if I open a file on both the guest and host, and write some data to the drive on the (macOS) host, the time until it shows up in the (Linux) guest is inconsistent (more specifically, it seems that the data won't show up in the guest unless I close the file and reopen it --- by contrast, if I write to the drive on the guest, it shows up nearly instantaneously on the host).
next reply other threads:[~2024-09-03 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 18:13 DUO Labs [this message]
2024-09-03 20:31 ` [Question] [Block] Is there a way to control the read caching of a block device? Philippe Mathieu-Daudé
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=d5f6c856-169d-4dcd-acd3-d42d886df17f@gmail.com \
--to=dvdugo333@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 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).