From: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
To: virtualization@lists.linux-foundation.org
Subject: 0-copy (was Re: question: asynchronous notification from vhost)
Date: Tue, 15 Oct 2019 16:42:04 +0200 [thread overview]
Message-ID: <20191015144203.GA1829@ubuntu> (raw)
In-Reply-To: <20191015092313.GA31275@ubuntu>
On Tue, Oct 15, 2019 at 11:23:13AM +0200, Guennadi Liakhovetski wrote:
> Hi,
>
> I'm developing a virtualised audio / DSP virtio and vhost driver pair
> and I'm currently somewhat stuck trying to figure out how to
> asynchronously notify the guest from the vhost driver. I'm using the
> vhost_add_used_and_signal() function to return data back to the guest
> in the guest context, when the guest initiated an operation, that's
> working well. But how do I "kick" the guest from an asynchronous, e.g.
> from an interrupt thread context?
I think I've solved that by using a vhost work queue. That brings me
one step further, possibly, to the last larger problem to solve: the
actual data transmission. My preference would be to use zero-copy
for that, but so far I only see one example of zero-copy in
drivers/vhost - in net.c and only in TX direction. As far as I
understand that isn't a principal limitation of the vhost / virtio
API, rather it's related to certain networking specifics. Am I
right? Is it supposed to work in both firections, or are there
problems?
Thanks
Guennadi
prev parent reply other threads:[~2019-10-15 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 9:23 question: asynchronous notification from vhost Guennadi Liakhovetski
2019-10-15 14:42 ` Guennadi Liakhovetski [this message]
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=20191015144203.GA1829@ubuntu \
--to=guennadi.liakhovetski@linux.intel.com \
--cc=virtualization@lists.linux-foundation.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).