From: Dmitry Fleytman <dmitry.fleytman@gmail.com>
To: qemu-devel@nongnu.org
Cc: mst@redhat.com, stefanha@redhat.com
Subject: [RFC] Per-request private data in virtio-block
Date: Wed, 10 Jul 2024 13:08:03 +0300 [thread overview]
Message-ID: <20240710100803.6644-1-dmitry.fleytman@gmail.com> (raw)
Hello QEMU-DEVEL! It's been a while…
I work on a solution for "smart" IO caching on the host side.
The configuration is virtio-block device backed by SPDK with OCF/OpenCAS
on top of remote storage.
To improve decision making for caching, I would like to have an additional
per-request contextual information from the guest side. It might include
information about process issuing an IO request, a file this request it tied
to and so on. In general, I'd like the set of collected information to be
flexible and configurable.
I searched mailing lists and other related sources and surprisingly found no
mentions of the topic of having custom per-request data in virtio rings.
This makes me think that either I'm missing an obvious way of doing this
or the concept itself is severely broken up to the point it's not even
getting discussed. There is also a possibility that I'm just missing a proper
search keywords...
I understand there might be be security implications to be considered.
Also having custom kernel patches to have a flexibility of choosing which
data to collect is probably not a viable solution.
Please share your thoughts.
I would like understand what is the right way of doing what I'm looking for.
If there are new mechanisms to be implemented in virtio or other parts of
the codebase, I'll gladly work on this for the sake of community.
Thank you,
Dmitry
next reply other threads:[~2024-07-10 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 10:08 Dmitry Fleytman [this message]
2024-07-10 16:56 ` [RFC] Per-request private data in virtio-block Stefan Hajnoczi
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=20240710100803.6644-1-dmitry.fleytman@gmail.com \
--to=dmitry.fleytman@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).